discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Gorm segfault on exit


From: Riccardo Mottola
Subject: Re: Gorm segfault on exit
Date: Fri, 22 Feb 2013 18:24:49 +0100
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15.2

Fred Kiefer wrote:
On 22.02.2013 14:15, Riccardo Mottola wrote:
when I start Gorm and close it, no problem. When I start it and open a
copuple of gorm files, everything file. If I open MDIndexer.m (of

Did you mean the MDIndexer.gorm file?
yes, sorry.


GWorkspace's Preferences, the one we are investigating about blur) Gorm
crashes on exist with the following segfault:

0xbb17ef1c in objc_msg_lookup () from /usr/lib/libobjc.so.3
(gdb) bt
#0  0xbb17ef1c in objc_msg_lookup () from /usr/lib/libobjc.so.3
#1  0xbb89fab3 in -[NSWindow resignKeyWindow] (self=0xba944e14,
     _cmd=0xbb9c6c50) at NSWindow.m:1880
#2  0xbb6fdb54 in -[NSApplication deactivate] (self=0xba7371b4,
     _cmd=0xba6f7c28) at NSApplication.m:1361
#3  0xba6b8359 in -[XGServer(EventOps) processEvent:] (self=Cannot
access memory at address 0xe000c
)
     at XGServerEvent.m:1152
#4 0xba6b321c in -[XGServer(EventOps) receivedEvent:type:extra:forMode:] ( self=0xba8201c4, _cmd=0xbb633b28, data=0x7, type=ET_RDESC, extra=0x7,
     mode=0xba9ca144) at XGServerEvent.m:310
#5  0xbb4550d3 in -[GSRunLoopCtxt pollUntil:within:] (self=0xba72ba64,
     _cmd=0xbb5ef628, milliseconds=0, contexts=0xba9e9d84)
     at GSRunLoopCtxt.m:494
#6  0xbb385318 in -[NSRunLoop acceptInputForMode:beforeDate:] (
     self=0xba9e9d24, _cmd=0xbb5ef648, mode=0xba9ca144,
     limit_date=<optimized out>) at NSRunLoop.m:1206
<snip>

I was able to reproduce a segmentation fault once. Next I tried in gdb, but could not reproduces it and since then I fail to get it even without gdb. I will fire up valgrind and see if that finds any anomaly. From you back trace it looks like the issue involves notifications and events, this could be very timing sensitive.

The error itself seems to come from an invalid first responder in the window. But which window? Could you try to print out some information on the window?
Here it looks very consistent. The window on #1, shows this:

<GormNSWindow: 0xba944f24>Number: 31 Title: Window
Thus it looks to me that it is one of the Gorm windows (given the class name, but also the Title). However all the document windows are caled Window... I suppose it is the window with the tabview, because that one is key.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]