Exception problem in C++

[Robert Schweikert <rjschwei at mindspring dot com>]

Does anyone have any ideas what could have gone wrong when the traceback
includes __throw() as follows?

Program terminated with signal 6, Aborted.
#0  0x411c44e1 in __kill () from /lib/libc.so.6
#0  0x411c44e1 in __kill () from /lib/libc.so.6
#1  0x4119b1eb in raise (sig=6) at signals.c:64
#2  0x411c5868 in abort () at ../sysdeps/generic/abort.c:88
#3  0x404b340b in __default_terminate ()
   from /usr/abaqus60/5-adb/object/linux32/exec/lbr/libHKSodbO.so
#4  0x404b342c in __terminate ()
   from /usr/abaqus60/5-adb/object/linux32/exec/lbr/libHKSodbO.so
#5  0x404b3d24 in throw_helper (eh=0x404e0970, pc=0x410aa8ee,
    my_udata=0xbfffecf8, offset_p=0xbfffecf4)
   from /usr/abaqus60/5-adb/object/linux32/exec/lbr/libHKSodbO.so
#6  0x404b3edc in __throw ()
   from /usr/abaqus60/5-adb/object/linux32/exec/lbr/libHKSodbO.so
#7  0x4085f2ed in ipc_Monitor::ShutDown ()
   from /usr/abaqus60/6-0/object/linux32/exec/lbr/libHKSipc.so

This happens on shutdown of an application. There is an exception being
thrown in "ipc_Monitor::ShutDown ()", which is in a shared library. This
exception is suppossed to be caught by main, which is further down in
the call stack. The problem is that we never get to the "catch" and
things gow wrong somewhere in between.

Further I found the following symbols defined in the libHKSodbO.so
shared library.

-> nm -Bg libHKSodbO.so | grep throw
00088f08 T __rethrow
000886d4 T __sjpopnthrow
000885c4 T __sjthrow
00088e48 T __throw
00089534 T __throw_bad_cast
000895d8 T __throw_bad_typeid
00088438 T __throw_type_match
0008af28 T __throw_type_match_rtti
0009a75f R nothrow

How do these symbols get defined and when? They do not show up when I
look at the individual object files prior to creating the shared
library.

Any help on this is appreciated.

Thanks,
Robert

--
Robert Schweikert                      MAY THE SOURCE BE WITH YOU
rjschwei@mindspring.com                         LINUX