gcc-20010409 and throw()

gcc-20010409 and throw()

[Simon Gee]

Hello,

I was just wondering what the state of this snapshot was wrt throw/catch
blocks (with a mips*-linux target). At present I have compiled this
snapshot (as well as gcc-20010402 and gcc-20010329) with a mipsel-linux
target and all produce binaries that return a SIGABRT from code that use
throw/catch blocks. An example of this behaviour is through the
compilation of the testsuite program element_access.cc whose resultant
stack trace from gdb is as follows:

Program received signal SIGABRT, Aborted.
0x2aad0c54 in kill () from /lib/libc.so.6
(gdb) where
#0  0x2aad0c54 in kill () from /lib/libc.so.6
#1  0x2aad0a50 in raise () from /lib/libc.so.6
#2  0x2aad29cc in abort () from /lib/libc.so.6
#3  0x40f04c in __default_terminate ()
#4  0x40f08c in __terminate ()
#5  0x410904 in __throw ()
#6  0x41372c in _ZSt20__throw_out_of_rangePKc ()
#7  0x4239fc in _ZNKSs2atEj ()
#8  0x40e454 in _Z6test01v () at element_access.cc:59
#9  0x40ecf4 in main () at element_access.cc:94
#10 0x2aac46cc in __libc_start_main () from /lib/libc.so.6
(gdb)

Any information/comments/advice would be appreciated.

Thanks in advance,

Simon