On 13.03.2006, at 18:53, Jim Ingham wrote: Alex,
The "exited with status 1" is usually because gdb has come across some "internal error" and is bailing out. There's a bug in gdb/Xcode that causes the error message not to get printed to the Xcode console. If you run your app under command-line gdb, to the same point where you got the error, you will be able to see the message.
Thanks you for your hints!
This is what I get in the console:
/SourceCache/gdb/gdb-437/src/gdb/macosx/macosx-nat-infthread.c:146: internal-error: assertion failure in function "prepare_threads_after_stop": tp != NULL What's happening in your release mode seems different. For some reason, your app's stopping in -[NSLayoutManager(NSPrivate) _mergeLayoutHoles], and then Xcode is calling some functions in the target to do some data inspection, and those are crashing. If you turn off the data formatters (uncheck Debug->Variables View->Enable Data Formatters) then Xcode will not ask gdb to call this code, and you can at least see why you are stopping there.
Disabling the Data Formatters causes this stack trace on crash:
#0 0x9342251e in -[NSLayoutHole compare:] #1 0x9081e1d1 in CFQSortArray #2 0x9081dfe2 in CFArraySortValues #3 0x927055a6 in -[NSCFArray sortUsingFunction:context:] #4 0x927054fb in -[NSMutableArray sortUsingSelector:] #5 0x934225b0 in -[NSSortedArray setCompareSelector:] #6 0x9340f5af in -[NSLayoutManager(NSPrivate) _mergeLayoutHoles] #7 0x9343de23 in +[NSLayoutManager(NSPrivate) _doSomeBackgroundLayout] #8 0x9343db22 in _NSPostBackgroundLayout #9 0x90823419 in __CFRunLoopDoObservers #10 0x908224bb in CFRunLoopRunSpecific #11 0x90822179 in CFRunLoopRunInMode #12 0x92ed28e0 in RunCurrentEventLoopInMode #13 0x92ed1fe7 in ReceiveNextEventCommon #14 0x92ed1e3e in BlockUntilNextEventMatchingListInMode #15 0x93372ad1 in _DPSNextEvent #16 0x933726be in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] #17 0x9336c443 in -[NSApplication run] #18 0x93360397 in NSApplicationMain #19 0x000026ae in _start at crt.c:272 If you want to file a bug about this, we can look into it further.
I have filed these as filed these as 4475677 and 4475695. It would be great if someone could take a look
Alex
|