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: "Peter CK" <email@hidden>
- Date: Mon, 3 Jul 2006 23:40:41 -0400
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.
Peter
On 7/3/06, Rob Rohan <email@hidden> wrote:
http://en.wikipedia.org/wiki/SIGSEGV
On Jul 3, 2006, at 1:45 PM, Peter CK wrote:
> Does anyone know what this means...
> "The Debugger has exited due to signal 11 (SIGSEGV).The Debugger has
> exited due to signal 11 (SIGSEGV)."
> I keep getting this when I'm debugging a plugin project. It terminates
> my application. Any ideas?
>
> Peter
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
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