Re: Corrupted stack
Re: Corrupted stack
- Subject: Re: Corrupted stack
- From: James Johnson <email@hidden>
- Date: Tue, 21 Feb 2006 17:08:55 -0800
How do you know the stack is corrupt? Are you reading this from gdb,
e.g. "warning: Previous frame pointer identical to this frame
(corrupt stack?)"?
The reason I ask is I've run into a similar problem and have not been
able to determine if the stack is indeed corrupt. My case the
application runs fine and tracing through the application mostly
works except for one section of code where gdb spits out these
warnings. In this section Xcode also duplicates automatic vars, but
only on the Intel platform (PPC is fine). There's nothing unique
about this code, no indexing into arrays or pointer use, nothing that
screams potential stack corruption. But it does return small struct
(8 bytes) on the stack.
To help in your effort, google "gdb stack corruption". There are a
few articles there, surprisingly, pertaining to PPC. Here are a few
that that may help you out.
http://ask.slashdot.org/article.pl?sid=06/01/11/0011218
http://devpit.org/wiki/GDB
http://lists.debian.org/debian-powerpc/2005/05/msg00201.html
Good luck!
James
On Feb 21, 2006, at 2:36 PM, email@hidden wrote:
Hi
I have a problem while debugging my application with xcode. Before
with codewarrior it was working fine.
The stack is corrupted before running the main() fonction. In
setting globals variable? or even before?
Any idea how I could "watch" at the stack.
Thanks
Vincent
_______________________________________________
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
_______________________________________________
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