libunwind-devel
[Top][All Lists]
Advanced

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

[Libunwind-devel] compilation errors involving _Unwind_Resume


From: Adam Portley
Subject: [Libunwind-devel] compilation errors involving _Unwind_Resume
Date: Tue, 26 Feb 2008 16:50:00 -0800 (PST)

Is this the correct mailing list for basic libunwind usage questions?  I tried subscribing at address@hidden as described in the package README and received an error message in reply.

I'm investigating libunwind as a possible replacement for backtrace() because backtrace occasionally deadlocks inside the signal handler - so I just need "local" unwinding.  My application is compiled on a 32-bit Red Hat node with gcc 3.4.3, though it is often run on x86_64.  I built libunwind, installed to a scratch directory using "configure --prefix", and tried compiling:

3.4.3/bin/gcc -pipe -g -Wall -DUSE_EXCEPTIONS=1 -rdynamic -Wno-deprecated  -o myApp myApp.o ... <scratch-dir>/install/lib/libunwind.a .../gcc/3.4.3/lib/libstdc++.a -lm


and I get the following error:

/build/Linux_2.6_rh4_i686/tools/gcc/3.4.3/bin/../lib/gcc/i686-pc-linux-gnu/3.4.3/libgcc.a(unwind-dw2.o)(.text+0x1a10): In function `_Unwind_Resume':
/tools/gcc/build-3.4.3/gcc-3.4.3/gcc/unwind.inc:224: multiple definition of `_Unwind_Resume'
<scratch>/install/lib/libunwind.a(Resume.o)(.text+0x0):unwind/Resume.c:30: first defined here
/tools/binutils/2.15/bin/ld: Warning: size of symbol `_Unwind_Resume' changed from 399 in <scratch>/install/lib/libunwind.a(Resume.o) to 213 in <scratch>/install/lib/libunwind.a(Resume.o)

because (I guess) _Unwind_Resume is defined in libstdc++.a. 

Does this indicate an incompatibility somewhere, or am I doing something wrong?

Thanks,
--Adam.


Looking for last minute shopping deals? Find them fast with Yahoo! Search.
reply via email to

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