At work, one of my best tools for diagnosing resets on our embedded systems is addr2line. From a reset log, I can extract a stack trace, and run it through this tool.
Using the very same technique, I get *nothing* on my kernel. Perhaps someone can help me out here?
Even if I grab an address directly from nm, I get nothing!
> nm ndk.kernel
0010263e T vm86IntHandler
> addr2line -e ndk.kernel 10263e
??:0
Does this make sense? Perhaps I'm misusing these tools?
Thanks,
Jeff
addr2line
- carbonBased
- Member
- Posts: 382
- Joined: Sat Nov 20, 2004 12:00 am
- Location: Wellesley, Ontario, Canada
- Contact:
- carbonBased
- Member
- Posts: 382
- Joined: Sat Nov 20, 2004 12:00 am
- Location: Wellesley, Ontario, Canada
- Contact:
Re: addr2line
btw, I'm completely mental... I recall adding debug support into my build process, but apparently it was removed. The solution? Add -g to the compile line, of course
I really gotta think before I post...!
I really gotta think before I post...!