[libunwind] indirect calling libunwind by using exception handling?

[Mensing, Joerg]

Hi,
does linking with 'libunwind 0.96' directly influences gcc's own exception 
handling behaviour?

Is i.e. any C++ runtime library function overloaded?

And if it the case, is there any way to prevent this?

I would like to use 'libunwind 0.96' for stack backtrace only. It seems to work 
fine, but we are running into a problem

> (gdb) where
> #0  0x20000000001b46c0 in parse_lsda_header(_Unwind_Context*, 
> unsigned char const*, lsda_header_info*) ()
>    from /usr/lib/libstdc++.so.5
> #1  0x20000000001b4d60 in __gxx_personality_v0 () from 
> /usr/lib/libstdc++.so.5
> #2  0x40000000015b6f40 in _Unwind_Phase2 
> (exception_object=0x60000000002573a0, context=0x20009719860) 
> at unwind-internal.h:61
> #3  0x40000000015b6d70 in _Unwind_Resume 
> (exception_object=0x60000000002573a0) at _Unwind_Resume.c:37
> #4  0x2000000002234160 in 
> Cconsistent::DROP_CURRENT_SCHEMA(char (*) [64]) 
> (this=0x60000000002573a0, SchemaName=0x2000b5e8899)
>     at consistentObj.cpp:2674

when Cconsistent::DROP_CURRENT_SCHEMA() throw an exception. The problem is 
still under investigation...

Used versions

$ uname -a
Linux ls0103 2.4.21-112-itanium2-smp #1 SMP Tue Nov 4 12:58:13 UTC 2003 ia64 
unknown

$ rpm -qa | egrep "gdb|gcc"
libgcc-3.2.2-23
gcc-info-3.2.2-6
gcc-c++-3.2.2-6
gcc-g77-3.2.2-6
gcc-3.2.2-6
gdbm-1.8.0-557
gdb-5.3-101


I would really appreciate, if you could verify that this has nothing to do with 
using libunwind 0.96.

Best regards
Jörg Mensing
SAP AG
NW DT MaxDB&liveCache Berlin
Rosenthalerstr. 30
10178 Berlin