Re: Stack trace recoding on Mac OS X Leopard ( 10.5 )
Re: Stack trace recoding on Mac OS X Leopard ( 10.5 )
- Subject: Re: Stack trace recoding on Mac OS X Leopard ( 10.5 )
- From: Brett George <email@hidden>
- Date: Fri, 22 Aug 2008 09:23:44 -0700
Rohitash wrote:
> Hi,
> I was exploring of some interfaces in Mac OS X if present , which might
> help me get a call backtrace which I want to record for some specific
> internal exception conditions . If some kind of unwind library is
> already available for use , that would really help simplify my task .
>
> I am not sure if the BSD library backtrace() and friends should be able
> to help me walk through all the stack frames and provide me with the
> arguments , parameters and the translated
> PC ( to symbolic names ) at any point I want to get a trace the call stack.
>
> I was reading the man page of atos and it seemed like I can take some
> help from its source code.Also , there seems to be a call stack
> generated in "/Library/Logs/CrashReporter/" for any application level
> crashes, if I am not wronged in assuming.This makes me assume that the
> basic infrastructure already exists to dump the information , and maybe
> I should be on my way if I can use them for my purpose instead of
> writing it from scratch.
>
> Appreciate your valuable inputs.
>
> Thanks,
> Rohitash
>
Have a look at OSBacktrace in OSDebug.cpp, you can trace through the
stack with that.
You would still have to tie it in with the symbols though.
Brett.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden