Hi,
On 2018-08-01 13:33:39 +0200 Wolfgang Lux <[email protected]> wrote:
Hi Riccardo,
This stack trace looks fairly weird to me; it seems like the debug
info does
not match the code. This reminds me of situations where my programs
got
linked to two different versions of a GNUstep library (a newer one
used
directly from the application and an older one linked indirectly from
some
library/bundle that I forgot to recompile). You might check using
info sharedlibrary
from the gdb prompt and looking for more than one instance of
libgnustep-gui.so in the list.
It is indeed strange, I saw that too.. however the problem is quite
reproducable. I will clean & check on this system (Debian)
I got this trace from another computer (Gentoo)
It is clearly "corrupted". I guess that the _app_icon is invalid.
Program received signal SIGSEGV, Segmentation fault.
0xb7b356a2 in -[NSApplication setApplicationIconImage:] (
self=0xb7b329d3 <-[NSApplication(Private) _loadAppIconImage]+483>,
_cmd=0x537200,
anImage=0xb7ece238 <_OBJC_SELECTOR_TABLE+3256>) at NSApplication.m:2392
2392 imageSize = [_app_icon size];
(gdb) bt
#0 0xb7b356a2 in -[NSApplication setApplicationIconImage:] (
self=0xb7b329d3 <-[NSApplication(Private) _loadAppIconImage]+483>,
_cmd=0x537200,
anImage=0xb7ece238 <_OBJC_SELECTOR_TABLE+3256>) at NSApplication.m:2392
#1 0x005ac9d0 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) p _app_icon
$1 = (struct NSImage *) 0x2474ff55
(gdb) po _app_icon
Cannot access memory at address 0x2474ff55
If I back out exactly the two commits from Gregory, Ink (as well as
other apps, I'm using Ink only for simplicity) starts again.
Riccardo
_______________________________________________
Discuss-gnustep mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnustep
