Re: Stack overflow detection/Stack use over time
Re: Stack overflow detection/Stack use over time
- Subject: Re: Stack overflow detection/Stack use over time
- From: Andreas Grosam <email@hidden>
- Date: Fri, 2 Apr 2010 19:32:27 +0200
On Apr 1, 2010, at 3:52 PM, Guillaume Billard wrote: Hello,
We've been experiencing "random" crashes in our app recently, that were seemingly caused by a stack overflow. Increasing the stack size for one of the threads made the crashes go away. There are about 8 threads running during the whole life of the application. Crashes happened at randoms locations, and most of the time GDB could not display a callstack or just a small part of it. The app would always stop with GDB dislaying this message: - "Program received signal: “EXC_BAD_ACCESS”."
And a combination of these: - "Previous frame inner to this frame (gdb could not unwind past this frame)" ..
This could also be caused by a zombie going havoc and corrupting the stack. Or any data structure that became corrupt. Well, many reasons. So, you should activate the usual memory checkers:
Andreas |
_______________________________________________
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