Re: Debugger Exits without info
Re: Debugger Exits without info
- Subject: Re: Debugger Exits without info
- From: Michael Rice <email@hidden>
- Date: Sat, 6 Jan 2007 13:09:32 -0600
You could install an exit handler using atexit() and then set a
breakpoint in your exit handler function. The debugger stack trace
should show you where exit() was called from.
Michael
On Jan 6, 2007, at 12:12 PM, Wesley Smith wrote:
Hi,
I'm trying to use the debugger in xcode to pinpoint where my app is
exiting. I have a few included libraries that could potentially be
calling exit(). Unfortunately, when this happens, I don't get any
stack info to see under what conditions and with what functions this
happens. I just get Program exitited with status:1.(gdb). Is there a
way to capture this information?
thanks,
wes
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40knology.net
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