Re: The Debugger has exited with status 1
Re: The Debugger has exited with status 1
- Subject: Re: The Debugger has exited with status 1
- From: Jim Ingham <email@hidden>
- Date: Mon, 13 Mar 2006 09:53:01 -0800
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.
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.
If you want to file a bug about this, we can look into it further.
Jim
On Mar 13, 2006, at 9:24 AM, Alexander von Below wrote:
On 10.03.2006, at 17:15, Jonathan del Strother wrote:
On 10 Mar 2006, at 15:59, Alexander v. Below wrote:
Hello List, I am getting the message
"The Debugger has exited with status 1.The Debugger has exited
with status 1." (gdb 6.1, Intel)
at not really determinable points when debugging my application,
and without any sort of useful information. Sometime, when I step
through the code, it will never come up, when I hit "continue"
the debugger sometimes quits here, sometimes there, sometimes not
at all.
Are you using QTKit, or debugging something attached to iTunes,
anything like that? These can cause a few debugging problems
similar to what you're seeing - eg if you try and open up a
protected audio file.
If that *is* your problem, try breaking on ptrace, and forcing an
early return before it gets chance to kill the debugger.
I am not using QTKit or attaching to iTunes. I am using core audio
though, but I doubt that is the problem. When I run my code from
Xcode in release mode, I get an bad access with this stacktrace:
#0 0x9000321a in malloc
#1 0x000025e0 in <function called from gdb>
#2 0x9340f686 in -[NSLayoutManager(NSPrivate) _mergeLayoutHoles]
#3 0x9343de23 in +[NSLayoutManager(NSPrivate) _doSomeBackgroundLayout]
#4 0x9343db22 in _NSPostBackgroundLayout
#5 0x90823419 in __CFRunLoopDoObservers
#6 0x908224bb in CFRunLoopRunSpecific
#7 0x90822179 in CFRunLoopRunInMode
#8 0x92ed28e0 in RunCurrentEventLoopInMode
#9 0x92ed1fe7 in ReceiveNextEventCommon
#10 0x92ed1e3e in BlockUntilNextEventMatchingListInMode
#11 0x93372ad1 in _DPSNextEvent
#12 0x933726be in -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:]
#13 0x9336c443 in -[NSApplication run]
#14 0x93360397 in NSApplicationMain
#15 0x000026ee in _start at crt.c:272
#16 0x00002609 in start
None of this appears to be my code, where could I even start to
look? Another problem is that I first will have to remove some
Apple functions that fail with GuardMalloc on the Intel machine (I
filed a bugreport already) to see if it is memory related.
Any help would be really appreciated on theis
Thanks
Alex
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden