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: "Ivan Cavero Belaunde" <email@hidden>
- Date: Wed, 5 Jul 2006 09:27:31 -0700
- Thread-topic: Debugger has exited due to signal 11 (SIGSEGV)
FYI, it’s not
just iTunes. You can still get the same signal 11 you get from iTunes from your
own QT apps if you’ve opened an M4P file for playing.
From:
xcode-users-bounces+icavero=email@hidden
[mailto:xcode-users-bounces+icavero=email@hidden] On Behalf Of Peter CK
Sent: Tuesday, July 04, 2006 1:20
PM
To: Xcode List
Subject: Re: Debugger has exited
due to signal 11 (SIGSEGV)
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.
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 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.
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?
Peter
|
_______________________________________________
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