Follow-up Comment #7, bug #24785 (project gnustep): Thank you for this information. Now at least we ahve an idea why this strange behaviour could happen.
I am not sure whether this is related, but after Richards patch to better report exceptions I did get the following when closing a process: Program received signal SIGABRT, Aborted. [Switching to Thread 0xb73c38d0 (LWP 9905)] 0xffffe430 in __kernel_vsyscall () (gdb) bt #0 0xffffe430 in __kernel_vsyscall () #1 0xb76ac900 in raise () from /lib/libc.so.6 #2 0xb76ae238 in abort () from /lib/libc.so.6 #3 0xb7cc0522 in _NSAppKitUncaughtExceptionHandler (exception=0x8560960) at NSApplication.m:148 #4 0xb7971a53 in callUncaughtHandler (value=0x8560960) at NSException.m:732 #5 0xb79721d1 in -[NSException raise] (self=0x8560960, _cmd=0xb7fa04c8) at NSException.m:867 #6 0xb7e5bd99 in -[_GSWorkspaceCenter postNotification:] ( self=0x86319d0, _cmd=0xb7fa04e8, aNotification=0x857a8d8) at NSWorkspace.m:336 #7 0xb7e5beb5 in -[_GSWorkspaceCenter postNotificationName:object:userInfo:] (self=0x86319d0, _cmd=0xb7f05898, name=0xb7faacd0, object=0x8631750, info=0x857a8a8) at NSWorkspace.m:353 #8 0xb7cca52c in -[NSApplication replyToApplicationShouldTerminate:] ( self=0x82473d8, _cmd=0xb7f05ca0, shouldTerminate=1 ' _______________________________________________ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep