If it's i386, do you have symbols for the functions you're stepping
around, or have you stripped the symbols from your binaries (e.g.
people often strip almost all the symbols from a plugin). gdb
inspects the prologue of functions on i386 to determine how the stack
is being used to backtrace; if it can't find the starting address of
the function it has to make a guess about how to backtrace out. And
that guess is not always correct.
If you can provide more specific details, a reproducible case would be
ideal, please file a bug report at http://bugreport.apple.com/
J
On Jun 30, 2008, at 5:56 PM, Romain Marucchi wrote:
Error from Debugger: Previous frame inner to this frame (gdb could
not unwind past this frame)
How can I debug that? and how can I get the call stack? GDB doesn't
show me where it crash and from which call in my code. Only if I
step through I can see where it pop but that extremely slow to debug
like that... please help
Tks in advance,
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/xcode-users/jmolenda
%40apple.com
This email sent to 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:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
This email sent to email@hidden
References:
>GDB Problem (From: Romain Marucchi <email@hidden>)
