backtrace of the current process execution

backtrace of the current process execution

[laurent.marzullo]

Hello,

I would like to know if there's a way to know the call stack of a running
process into the process itself ?

I wrote a C++ program ... and when throwing exception, I would like to
print the full call stack to std::cerr. Is there a way to do so with
libgdb ? or any other lib ?

Thanks a lot
Laurent Marzullo

Re: backtrace of the current process execution

[Andreas Schwab]

laurent.marzullo@one-d.com writes:

> I would like to know if there's a way to know the call stack of a running
> process into the process itself ?

Try the backtrace function from <execinfo.h>.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: backtrace of the current process execution

[Bob Rossi]

On Fri, Dec 03, 2004 at 04:14:27PM +0100, Andreas Schwab wrote:
> laurent.marzullo@one-d.com writes:
> 
> > I would like to know if there's a way to know the call stack of a running
> > process into the process itself ?
> 
> Try the backtrace function from <execinfo.h>.
> 
> Andreas.

I think you can link to valgrind and it knows how to give backtrace's
via a macro at any point in your code.

Bob Rossi

Re: backtrace of the current process execution

[Andrew Burgess]

On Fri, 03 Dec 2004 16:14:27 +0100, Andreas Schwab <schwab@suse.de> wrote:

> laurent.marzullo@one-d.com writes:
>
>> I would like to know if there's a way to know the call stack of a  
>> running
>> process into the process itself ?
>
> Try the backtrace function from <execinfo.h>.

This is handy but gives no _static_ symbols. I start with backtrace()
and then create a pipe to addr2line (part of binutils). This gives
static symbols and the exact line numbers. You could also post-process with
addr2line I suppose...

Now if it only printed arguments like gdb...

It really seems like a useful feature for a libgdb since gdb already
knows how to do it.

HTH