This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/12555] New: exception handling fails when shared lib is dlopened in process
- From: "bim2003 at basistech dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 9 Oct 2003 18:48:30 -0000
- Subject: [Bug libstdc++/12555] New: exception handling fails when shared lib is dlopened in process
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12555
Summary: exception handling fails when shared lib is dlopened in
process
Product: gcc
Version: 3.2.3
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: bim2003 at basistech dot com
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
The attachments here will allow you to demonstrate the following problem.
With glibc-2.2.4-32.8 (on, as it happens, RedHat AS 2.1), if a C++ program
dlopens a library (the example is python) and then dlopens and calls into a
second library, and the code in the second library catches an exception and
then throws that exception in the scope of the block, the catch fails to catch
the exception and the program aborts.