public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nagaraj_hayyal at satyam dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13878] Uncaught exception on AIX with shared libraries
Date: Tue, 31 May 2005 12:54:00 -0000 [thread overview]
Message-ID: <20050531122210.2629.qmail@sourceware.org> (raw)
In-Reply-To: <20040127083113.13878.joerg.richter@pdv-fs.de>
------- Additional Comments From nagaraj_hayyal at satyam dot com 2005-05-31 12:21 -------
(In reply to comment #5)
Did you get any solution for this?
We are experiencing the same problem here.
Please let us know the solution if you have already found one.
mail: Nagaraj_Hayyal@satyam.com
> Our project is also experiencing problems with exceptions not being caught,
when
> compiling with g++ on AIX. Small example codes that we have tried to put
> together to model what we are seeing, do not end up having the same incorrect
> behavior. On large test cases (our entire application as linked by g++), any
> exceptions thrown (that make it into _cxa_throw) do not bubble up to the
catch
> statement (not even a literal catch(...)); rather, all exceptions call abort
().
> I would be extremely interested in hearing how this issue sorts itself out. I
> can try to give you more feedback no our problem than this, if requested. At
the
> moment we are not sure what the property is that is required in order for the
> exception handling behavior to go from good to bad. That is work in progress.
> This occurs on AIX 5, GCC 3.3.2.
> Greg Smethells
> Lawrence Livermore National Lab
> smethells@llnl.gov
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13878
prev parent reply other threads:[~2005-05-31 12:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 8:31 [Bug c++/13878] New: " joerg dot richter at pdv-fs dot de
2004-01-31 0:43 ` [Bug c++/13878] " dhazeghi at yahoo dot com
2004-02-01 2:52 ` dje at watson dot ibm dot com
2004-02-01 10:26 ` joerg dot richter at pdv-fs dot de
2004-02-21 19:12 ` greed at pobox dot com
2004-03-01 21:01 ` smethells at llnl dot gov
2004-03-03 20:52 ` ajd at gentrack dot com
2004-03-03 22:50 ` dje at gcc dot gnu dot org
2004-03-03 22:51 ` dje at gcc dot gnu dot org
2004-03-03 22:54 ` dje at watson dot ibm dot com
2004-03-06 20:55 ` dje at gcc dot gnu dot org
2004-03-06 23:31 ` pinskia at gcc dot gnu dot org
2004-03-07 22:37 ` dje at gcc dot gnu dot org
2005-05-31 12:54 ` nagaraj_hayyal at satyam dot com [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050531122210.2629.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).