Apple

On Sep 27, 2006, at 12:01 PM, Eric Albert wrote:

On Sep 27, 2006, at 1:52 AM, email@hidden wrote:

could be a bit off list

i have a crashlog with the following info:

Thread 9 Crashed:
0   px 0x00c12430 px3claimobject::claim(unsigned char*) + 404 (px3claimobject.cp:343)
1   px 0x00c0ee90 px3claimobjectatomic::claimwaitfor() + 220 (px3claimobject.cp:150)
2   px 0x004a9438 pxlist::cleanup() + 308 (pxlist.cp:126)
3   px 0x004a8bf0 pxlist::~pxlist [in-charge]() + 72 (pxlist.cp:107)
4   px 0x00606f24 px_filter_param::whereclause(pxsession*, px3s*) + 1532 (pxreportfilterparam.cp:829)
5   px 0x0059bdd0 pxfilter::whereclausediscardnegation_synfilter(pxsession*, px3s*, px3s*) + 912 (pxlistfilter.cp:289)
6   px 0x00590b30 pxfilter::whereclausediscardnegation(pxsession*, px3s*, px3s*) + 1880 (pxlistfilter.cp:81)
7   px 0x0058fde0 pxfilter::whereclause(pxsession*, px3s*, px3s*) + 1032 (pxlistfilter.cp:52)
8   px 0x00535b54 pxlist::whereclause(pxsession*, px3s*, px3s*) + 1356 (pxlist_query.cp:71)
9   px 0x00551608 pxlist::runquery_core(pxsession*) + 2492 (pxlist_query_core.cp:128)
10 px 0x0053dcbc pxlist::runquery(pxsession*, unsigned char) + 612 (pxlist_query.cp:256)

obviously the system crashed at the function

px3claimobject::claim(unsigned char*)

at an offset of

+ 404

q: how do i determine the code line in wich it crashed

It's relatively straightforward for this crash log. You look at the line where you got the function name and the offset, and read a bit beyond that:
0   px 0x00c12430 px3claimobject::claim(unsigned char*) + 404 (px3claimobject.cp:343)

See the "px3claimobject.cp:343"? That's your file name and line number.

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

i thinnk the +404 is the offset for the crashing instruction...but at what is the instruction itself, what line?

Hope this helps,
Eric

References:
	>interpreting crashlog (From: email@hidden)
	>Re: interpreting crashlog (From: Eric Albert <email@hidden>)