Re: Corrupt stack?
Re: Corrupt stack?
- Subject: Re: Corrupt stack?
- From: Lawrence Gold <email@hidden>
- Date: Fri, 15 Jun 2007 10:34:38 -0600
On Jun 14, 2007, at 4:58 PM, Yves Poissant wrote:
When I run my application in debug build, 50% of the time, I get an
error "Error from Debugger: Previous frame inner to this frame
(corrupt stack?)". Most of the time, if I run the application
again, I won't have this error a second time.
The stack dump does not give me any clue as to what happened and
where this happened. The stack dump looks like this:
#0 ???
#1 0x00000001 in ???
And when I examine the values in memory at $ebp address, the frames
don't make any sense. I mean, it is really off.
So, I'm wondering. Should I worry about that? I mean is this
indicative of a memory overrun in my code or is this really a GDB
thing? If I should worry about something wrong in the application
code, what would be a good strategy to figure what and where the
bug is happening? Any suggestions?
I've seen odd behavior in the IDE regarding the debugger, and
recommend that you try GDB from the command line to see if the
problem persists. If it does, then it's possible that you're seeing a
stack overflow. If your app is multithreaded and the messed up stack
is happening in a worker (non-main) thread, try increasing the
thread's stack size. The main thread on OS X is given an 8MB stack by
default, so it's unlikely you're overflowing unless you have some
gigantic stack-based arrays or something. :-)
_______________________________________________
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