[LLVMdev] exception handling bug?

Neal Becker ndbecker2 at gmail.com
Wed Nov 12 08:05:20 PST 2008

Compiled boost-1.37.0 using llvm-2.4 (OK).  Attempting to use it I get:

Program received signal SIGSEGV, Segmentation fault.
0xfffffffffd4c3720 in ?? ()
(gdb) where
#0  0xfffffffffd4c3720 in ?? ()
#1  0x00000033fc810c66 in _Unwind_RaiseException () from /lib64/libgcc_s.so.1
#2  0x00000033fd4c3dbd in __cxa_throw () from /usr/lib64/libstdc++.so.6
#3  0x0000000000636df3 in boost::python::throw_error_already_set () from /usr/local/src/boost-llvm.hg/stage/lib/libboost_python.so
#4  0x000000000063a82f in boost::python::objects::stop_iteration_error () from /usr/local/src/boost-llvm.hg/stage/lib/libboost_python.so

This tells me exception handling isn't working right.  boost::python should have caught this exception and returned it to python.

More information about the llvm-dev mailing list