Update of bug #15612 (project gnustep):
Open/Closed: In Test = Closed
___
Follow-up Comment #6:
Tested and confirmed this is not happening. No feedback from submitter.
Update of bug #15612 (project gnustep):
Category:None = Gui/AppKit
Status:None = Fixed
Assigned to:None = CaS
Open/Closed:
Follow-up Comment #4, bug #15612 (project gnustep):
I mean a notification whose userInfo dictionary did not contain a key
'NSApplicationName' (I guess you would call that 'badly formed').
The stack trace looks like this was the application aqctivation notification,
but I checked the
Follow-up Comment #3, bug #15612 (project gnustep):
Gorm is now launching without hurdle. Thanks Richard.
How did that bad notification get sent to my Gorm copy… well I have no
idea.
By 'bad' notification, do you mean 'not well formed' or 'wrongly sent' ?
I'm not sure, but -[NSApplication
Update of bug #15612 (project gnustep):
Severity: 5 - Blocker = 2 - Minor
___
Follow-up Comment #2:
I've reclassed this as minort rather than closing it.
I've changed the code in GSLaunched() to
URL:
http://savannah.gnu.org/bugs/?func=detailitemitem_id=15612
Summary: Exception on Gorm launch with latest SVN (r22413)
Project: GNUstep
Submitted by: qmathe
Submitted on: ven 03.02.2006 à 01:40
Category: None
Follow-up Comment #1, bug #15612 (project gnustep):
Here is a complete stack trace as promised.
#0 -[NSException raise] (self=0x84a53c8, _cmd=0xb7aa2020) at
NSException.m:147
#1 0xb7881108 in -[GSMutableDictionary setObject:forKey:] (self=0x84a5278,
_cmd=0xb7dbeb90, anObject=0x0,
