[MacPorts] #45309: gimp2 @2.8.14 on 10.9 - doesn't load plug-ins
MacPorts
noreply at macports.org
Tue Oct 21 23:17:26 PDT 2014
#45309: gimp2 @2.8.14 on 10.9 - doesn't load plug-ins
---------------------------+----------------------
Reporter: and.damore@… | Owner: devans@…
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: gimp2 |
---------------------------+----------------------
Comment (by zhu527812567@…):
Replying to [comment:23 macports@…]:
For the core files,
the backtrace prints something like (frame 0 is 0x00000001069589e0 on my
machine)
{{{
* frame #0: 0x00000001069589e0
frame #1: 0x00007fff98a4b17e libsystem_c.dylib`fork + 29
frame #2: 0x000000010471bf43 libglib-2.0.0.dylib`fork_exec_with_pipes
+ 277
frame #3: 0x000000010471ba5d libglib-2.0.0.dylib`g_spawn_sync + 334
}}}
OR lldb reports
{{{ error: core file does not contain 0x1069589e0 }}}
The debugger cannot find {{{ 0x00000001069589e0 }}}. One possible cause is
that the address does not point to valid executable instructions at all.
{{{
-> 0x1069589e0: addb %al, (%rax)
0x1069589e2: addb %al, (%rax)
0x1069589e4: addb %al, (%rax)
0x1069589e6: addb %al, (%rax)
.... (many identical instructions)
}}}
The machine code (binary representation) for the instruction is binary
zero, so maybe a zero page
{{{
(lldb) dis -s 0x0000000106958000
0x106958000: addb %al, (%rax)
0x106958002: addb %al, (%rax)
0x106958004: addb %al, (%rax)
0x106958006: addb %al, (%rax)
....
}}}
well, this means that {{{fork()}}} returns to an invalid address page
(which is filled with zero).
Not only this page, the pages before and after are all zeros. In this case
we cannot debug the child :( , since the kernel does not return to the
correct position in the child.
--
Ticket URL: <https://trac.macports.org/ticket/45309#comment:25>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list