[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Libunwind-devel] libunwind vs backtrace_symbols

From: Brendan Miller
Subject: [Libunwind-devel] libunwind vs backtrace_symbols
Date: Fri, 7 Aug 2009 13:56:18 -0700


I'm trying to get a better programmatic backtrace for my C++ code.
Right now I'm using backtrace and backtrace_symbols. backtrace_symbols
seems to be unable to pick up function names for static or anonymous
functions. Will libunwind handle this better?

Also, what platforms does libunwind support? My target is red hat
enterprise linux 4, x86. This is with gcc 3.4. Will this work for
libunwind and backtraces?

What about symbols? I'm using C++. Will libunwind give me direct
access to the function symbol so I can demangle it for human readable
output? backtrace seems to require that you parse the symbol out of
the rest of the line, which isn't a show stopper, but is kind of

I don't really need a cross platform solution, just something that
works better on linux. If libunwind isn't the best solution for linux,
could someone point me in the right direction?

Sorry if these questions aren't appropriate for the devel mailing
list. I couldn't find a libunwind users mailing list.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]