Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 May 2011 10:45:49 +0300
From:      George Liaskos <geo.liaskos@gmail.com>
To:        gtodd@iciti.ca
Cc:        chromium@freebsd.org
Subject:   Re: Any attempt to print with chromium causes sigsev
Message-ID:  <BANLkTi=2iJuzuA_9Z6Tce2yoSug73wSO_w@mail.gmail.com>
In-Reply-To: <20110525195202.73393.qmail@wawanesa.iciti.ca>
References:  <20110525195202.73393.qmail@wawanesa.iciti.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 25, 2011 at 10:52 PM,  <gtodd@iciti.ca> wrote:
> Hi, I think this is a well known bug? Should I file a PR on
> the port?
>
> The main chromium development platform seems to be Windows (and
> some Linux) where the bug does not manifest. Upstream they'd like
> bug reports with backtraces and patches! I am attempting to build
> a debug version of trunk to see if this has been resolved and get
> a meaningful trace on the crash with our latest version.
>
> These are non-trivial operations at this site ;-)
>
> Since this seems difficult to patch/fix for FreeBSD should the crash
> be mentioned in UPDATING or pkg-message?
>
> Regards,
>
> GRT

>From chrome/browser/browser_main_posix.cc:

     23 #if defined(OS_LINUX) && !defined(OS_CHROMEOS)
     24 #include "chrome/browser/printing/print_dialog_gtk.h"
     25 #endif

this seems to be a good starting point. It is in my todo list for some
time now :p
I will take a look at it.

Regards,

George



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTi=2iJuzuA_9Z6Tce2yoSug73wSO_w>