This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: How to get a backtrace from a C module
John Love-Jensen wrote:
>
> Hi Alex,
>
> Isn't backtrace and backtrace_symbols part of the GNU C Library?
>
> q.v. http://www.delorie.com/gnu/docs/glibc/libc_665.html
>
> Are you using the GNU C Library, or the Sun C Library?
>
> --Eljay
>
Hi Eljay,
Thanks for the reply. I thought so too...that's where I discovered the
example etc.
I am using the GNU C library (I think)...When I do a ldd on an executable
thus created I see the following:
....
librt.so.1 => /usr/lib/librt.so.1
libm.so.2 => /usr/lib/libm.so.2
libsocket.so.1 => /usr/lib/libsocket.so.1
libz.so.1 => /usr/lib/libz.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libpthread.so.1 => /usr/lib/libpthread.so.1
libc.so.1 => /usr/lib/libc.so.1 libaio.so.1 =>
/usr/lib/libaio.so.1
libmd5.so.1 => /usr/lib/libmd5.so.1
libgcc_s.so.1 => /usr/sfw/lib/libgcc_s.so.1
libmp.so.2 => /usr/lib/libmp.so.2
libscf.so.1 => /usr/lib/libscf.so.1
libdoor.so.1 => /usr/lib/libdoor.so.1
libuutil.so.1 => /usr/lib/libuutil.so.1
/platform/SUNW,Sun-Blade-2500/lib/libc_psr.so.1
/platform/SUNW,Sun-Blade-2500/lib/libmd5_psr.so.1
As libgcc_s.so.1 is in the path I would assume it is. But the compiler
can't find the execinfo.h file either that describes the prototype for these
functions let alone the functions themselves. Please help...
Alex
--
View this message in context: http://www.nabble.com/How-to-get-a-backtrace-from-a-C-module-tf2740773.html#a7678076
Sent from the gcc - Help mailing list archive at Nabble.com.