This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
middle-end/7907: Exception thrown from one shared object does not get caught in a different shared object
- From: dickman at bezeqint dot net
- To: gcc-gnats at gcc dot gnu dot org
- Date: 13 Sep 2002 11:51:36 -0000
- Subject: middle-end/7907: Exception thrown from one shared object does not get caught in a different shared object
- Reply-to: dickman at bezeqint dot net
>Number: 7907
>Category: middle-end
>Synopsis: Exception thrown from one shared object does not get caught in a different shared object
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: pessimizes-code
>Submitter-Id: net
>Arrival-Date: Fri Sep 13 04:56:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: dickman@bezeqint.net
>Release: unknown-1.0
>Organization:
>Environment:
Linux using mandrake 8.2 with gcc3.2
>Description:
If you throw an exception from one shared object and try to catch it from another one it does not get caught.
This bug appeared also in version 2.95.3, was fixed in version 3.0.x and somehow was reinserted to version 3.2
>How-To-Repeat:
Throw an exception from one shared object and attempt to catch it from another shared object.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: