Re: interpreting crashlog
Re: interpreting crashlog
- Subject: Re: interpreting crashlog
- From: Eric Albert <email@hidden>
- Date: Thu, 28 Sep 2006 14:40:20 -0700
On Sep 28, 2006, at 2:31 PM, Ken Worley wrote: On Sep 28, 2006, at 3:18 PM, Perry Winkel wrote: On Sep 27, 2006, at 5:12 PM, Lawrence Gold wrote:
On Sep 27, 2006, at 8:29 AM, Perry Winkel wrote:
yep, its the line number where the function definition starts what i was hoping for was that the line number would tell me where in the funcrion the crash appears, but it just leads me to the first line of the definition
When I've seen crashes like this a couple of times, they were due to a stack overflow. I would try increasing the stack size of the thread that's crashing.
possibly, how do i adjust the stack size, a lookup in the doc gave no results
Call pthread_attr_setstacksize before calling pthread_create...assuming you're using the pthread functions to create your threads.
In my experience, most of the cases in which a symboled crash log reports line numbers which seem unlikely are ones where the crash log is from an optimized binary. Divining line number information from optimized code, particularly with stabs (rather than DWARF), is a bit more of an art than a science and often involves looking at disassembly. If that's something you're not too inclined to do, I'd suggest running an unoptimized (-O0) version of your application and looking at the backtrace from crashing that one.
-Eric
|
_______________________________________________
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