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: Tue, 4 Jul 2006 13:49:19 -0700
Your e-mail client is failing to quote properly.
On Jul 4, 2006, at 1:19 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).
Well, actually both the plugin and the app are developed in house.
However I am using some third party libraries such as quicktime.
If the app is yours as well, then I'm not really sure. Gdb shouldn't
crash (unless you're calling ptrace, but I'm guessing that's not
happening here). I'm not sure I'd consider quicktime third party.
So are you telling me I need to get my hands dirty and catch this
signal from gdb directly? So does this mean that gdb is at fault
here and Xcode has nothing to do with it?
I don't know if you can get gdb to catch signals. Xcode really has
very little to do with gdb. It invokes gdb and acts as a GUI for gdb
but isn't involved in the actual debugging.
I guess I'm trying to figure out if this is beacuse I'm writing
crapy code, or it is because the tools I'm using are incompetent,
or both.
Hard to say without more information.
In either case, this is happening very randomly. I can't work cause
the debugger terminates my app speradically with no call stack. Is
this a sign that I need to dedicate some time to look for memory
leaks in my code? That's what this is all about right, invalid
memory access?
Is gdb killing your code or is gdb itself dying randomly. Memory
leaks and invalid memory access are two different things. If you're
accessing invalid memory, your program will be terminated (unless you
catch the signal), but that won't cause gdb to die.
--
Steve Checkoway
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