Description of problem: gdb cannot set up exception catching ("catch throw"); it simply segfaults. Version-Release number of selected component (if applicable): gdb-6.8.50.20090302-38.fc11.x86_64 How reproducible: Always. Steps to Reproduce: 1. Run "gdb python" 2. Type "catch throw" at the gdb prompt. Actual results: gdb prints: Function "__cxa_throw" not defined. Segmentation fault Expected results: No segfault. Additional info: This is on a fully patched Fedora 11, x86_64 system. gdb on a RHEL5 box (gdb-6.8-37.el5) does not crash given the same input. We're also pretty sure this used to work on Fedora 11; since gdb itself hasn't been updated for a while, perhaps it is an odd interaction with one of its dependencies (expat, for example, which was updated only a week ago) ?
gdb-6.8.50.20090302-39.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/gdb-6.8.50.20090302-39.fc11
As python is not linked with libstdc++ I am not sure what is the goal of such command, it will not catch the python exceptions this way. If you wanted to do so you should rather find some internal Python exception-throwing function and `break' on it instead. Also I can suggest moving to F-12 with more recent GDB.
That is not the point - I picked python because it's going to be present on most systems. The point is that gdb should not crash. ;)
gdb-6.8.50.20090302-39.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.