Re: [Gimp-developer] Gimp git on Mac Segfault
- From: su_v <suv-sf users sourceforge net>
- To: Jehan Pagès <jehan marmottard gmail com>
- Cc: gimp-developer <gimp-developer-list gnome org>
- Subject: Re: [Gimp-developer] Gimp git on Mac Segfault
- Date: Sun, 28 Jul 2013 07:42:34 +0200
On 2013-07-28 07:32 +0100, Jehan Pagès wrote:
yes I saw your message in the report too. Actually I was feeling this
would work your crash around when I wrote this patch. But that is
still not a fix. When you open the preferences and check the Interface
tab, then the language list, this list is empty now, right?
No, it lists all languages.
On 2013-07-28 07:31 +0100, Partha Bagchi wrote:
Are you using Macport? I don't use Macport and build all my
dependencies from scratch.
Yes, I use MacPorts for the dependencies.
[ fullquote below trimmed to avoid moderation ]
On Sun, Jul 28, 2013 at 5:19 PM, su_v <suv-sf users sourceforge net> wrote:
On my system (10.7.5), GIMP launches ok, but crashes when opening
the preferences. See stack trace in
<https://bugzilla.gnome.org/show_bug.cgi?id=704592#c6>
With your patch applied (and no other local changes), GIMP still
launches ok, and now no longer crashes when opening the preferences
dialog (see attached log).
On 2013-07-28 05:47 +0100, Jehan Pagès wrote:
Hey Partha, su_v,
could you test the following patch:
- copy it in your GIMP directory;
- apply it with this command from the GIMP directory:
patch -p0 < osx_crash.diff
- compile and try again.
I believe it would not fix your crash, because I did not change the
calls where your traces say it happens. Problem is that it apparently
crashes at strchr() but there are 5 of them in this function. Looking
at what seems to be the code in MacOSX of strchr(), looks like it may
be when the string is NULL, but in my code, I don't see anywhere where
this is supposed to be possible.
So unless you can run a debugger to know which exact strchr() line it
happens at, I added some debug output in the code. Just copy paste
anything which may be outputted before crash.
You will most likely have a whole bunch of lines on screen because I
want to cover as much ground as possible, so you can run like this:
$ ./gimp-2.9 --verbose >output.txt
Then send me the output.txt after the crash occurs.
Thanks.
Jehan
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]