Re: Debug error--gdb could not unwind past...
Re: Debug error--gdb could not unwind past...
- Subject: Re: Debug error--gdb could not unwind past...
- From: dct <email@hidden>
- Date: Mon, 19 Sep 2011 11:20:24 -0700
| Jens,
Thanks for the reply. But, in a way, it begs the issue of where to look and what to look for (& watch out for) in C/Obj-C code. My recent run-in suggests that passing faulty data to a function can do the trick. I assume that there are other ways too and it'd be nice to know if these are documented anywhere.
Thanks
On Sep 18, 2011, at 3:41 PM, Jens Alfke wrote: On Sep 18, 2011, at 12:09 PM, dct wrote: Still, I would like to know a bit more about the "Error from Debugger:Previous frame inner to this frame (gdb could not unwind past this frame)" error--conditions that cause it and strategies to counter it. Are you aware of any references?
Generally it’s a bug that causes data on the stack to be overwritten, like a buffer overflow in a local array variable. If this overwrites the return address on the stack, then the debugger can’t find out who called this function. (And if you weren’t in the debugger already, the app would crash when returning from the function or very soon thereafter.)
—Jens
|
_______________________________________________
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