[SOLVED BUT UNEXPLAINED] Framework load address from an exception log
[SOLVED BUT UNEXPLAINED] Framework load address from an exception log
- Subject: [SOLVED BUT UNEXPLAINED] Framework load address from an exception log
- From: Jerry Krinock <email@hidden>
- Date: Wed, 13 Mar 2013 13:37:01 -0700
Thanks to Nick Blievers who replied, off-list accidentally, I have an answer for this. We don't understand it, but it works, at least in this case.
The part of the call stack that I needed to symbolize is this:
2 CoreFoundation 0x00007fff907c234a -[NSArray arrayByAddingObject:] + 138
3 MyFramework 0x0000000100152704 MyFramework + 614850
4 MyFramework 0x0000000100152cd5 MyFramework + 616339
5 MyFramework 0x00000001000395db MyFramework + 202203
6 Foundation 0x00007fff92f34677 __NSThreadPerformPerform + 225
Find at the *lowest* call in MyFramework, line 5 in this case. As Nick pointed out to me,
0x00000001000395db - 202203 = 0x100008000
Voila! 0x100008000 is the actual load address of the framework. Simply use this when calculating the address for each line, including line 5, ask gdb for its info, and you get answers that call one another as expected. And at the top lies bug I was looking for.
Can anyone explain why this works, and generalize its applicability?
Jerry
_______________________________________________
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