------- Comment #5 from arun dot sharma at google dot com  2005-11-08 00:55 
-------
(In reply to comment #3)
> You know that glibc has an backtrace function which might be more friendly for
> your purpose?
> 

glibc backtrace dlopens libgcc and uses _Unwind_Backtrace() on amd64. glibc
backtrace has it's own problems (i.e. mallocs) which is why we're not using it.

See: 

http://sources.redhat.com/bugzilla/show_bug.cgi?id=1579


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24724

Reply via email to