Re: Gorm segfault on exit

[Fred Kiefer]

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?

> 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
> #7  0xbb384072 in -[NSRunLoop runMode:beforeDate:] (self=0xba9e9d24,
>      _cmd=0xbb616c40, mode=0xba9ca144, date=0xb920cd84) at NSRunLoop.m:1274
> #8  0xbb4047f6 in -[GSMessageHandle sendMessage:beforeDate:]
> (self=0xba979544,
>      _cmd=0xbb616e70, components=0xb922dba4, when=0xb920cd84)
>      at NSMessagePort.m:1030
> #9  0xbb408bf6 in -[NSMessagePort
> sendBeforeDate:msgid:components:from:reserved:] (self=0xba7f9f44,
> _cmd=0xbb5bab88, when=0xb920cd84, msgId=0,
>      components=0xb922dba4, receivingPort=0xb9e0ca24, length=16)
>      at NSMessagePort.m:1962
> #10 0xbb2c328c in -[NSConnection(Private) _sendOutRmc:type:]
> (self=0xb9e1ba04,
>      _cmd=0xbb5ba958, c=0xb961d324, msgid=0) at NSConnection.m:3426
> #11 0xbb2bba93 in -[NSConnection(GNUstepExtensions)
> forwardInvocation:forProxy:] (self=0xb9e1ba04, _cmd=0xbb5c37f0,
> inv=0xb92362c4, object=0xb9e5be84)
>      at NSConnection.m:2041
> #12 0xbb2ec4e5 in -[NSDistantObject forwardInvocation:] (self=0xb9e5be84,
>      _cmd=0xbb61a870, anInvocation=0xb92362c4) at NSDistantObject.m:606
> #13 0xbb4146fd in GSFFIInvocationCallback (cif=0xb960b0c0, retp=0xbfbfe368,
>      args=0xbfbfe300, user=0xb922db24) at GSFFIInvocation.m:629
> #14 0xbab139cb in ffi_closure_SYSV_inner (closure=0xb9f6a008,
>      respp=0xbfbfe374, args=0xbfbfe388) at ../src/x86/ffi.c:498
> #15 0xbab13bea in ffi_closure_SYSV () at ../src/x86/sysv.S:188
> #16 0xbb2eee87 in -[NSDistributedNotificationCenter
> postNotificationName:object:userInfo:deliverImmediately:]
> (self=0xb9e0c084, _cmd=0xbb5c4e30,
>      notificationName=0xbba841f4, anObject=0xbba7a80c, userInfo=0xb920dee4,
>      deliverImmediately=0 '\000') at NSDistributedNotificationCenter.m:435
> #17 0xbb2ee457 in -[NSDistributedNotificationCenter postNotification:] (
>      self=0xb9e0c084, _cmd=0xbba79f40, notification=0xb922daa4)
>      at NSDistributedNotificationCenter.m:369
> #18 0xbb8b97d6 in -[_GSWorkspaceCenter postNotification:] (self=0xb9d3b364,
>      _cmd=0xbba79f50, aNotification=0xb922d5c4) at NSWorkspace.m:340
>
> GWorkspace is NOT running.

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?


Fred