Re: Debugger has exited due to signal 11 (SIGSEGV)
Re: Debugger has exited due to signal 11 (SIGSEGV)
- Subject: Re: Debugger has exited due to signal 11 (SIGSEGV)
- From: Steve Checkoway <email@hidden>
- Date: Mon, 3 Jul 2006 23:57:32 -0700
On Jul 3, 2006, at 8:40 PM, Peter CK wrote: Ok, so I guess I have some invalid memory reference in my application. Why is it that Xcode doesn't catch this and give me a call stack that I can work with? Is there some type of data corruption caused by my error that prevents Xcode from showing me what's wrong?
Is there a good reason that Xcode is not being more coherent in this situation, or can I call this a bug. Could somebody give me a clue why this is acceptable behaviour for an IDE.
By the way, the plugin I'm debugging is one of my own, not a third party. Thanks for your help guys.
It's gdb itself that's getting the signal. The plugin is your own, but I'm guessing that the app you're debugging is not. The behavior you're seeing is consistent with what happens if you try to debug an app that has called ptrace with the option I mentioned in the last e-mail, such as iTunes (or so I've heard).
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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