From: David Edelsohn <dje@watson.ibm.com>
To: "Abhijit H. Bhosale" <abhibhosale@yahoo.co.uk>
Cc: gcc@gcc.gnu.org
Subject: Re: Throwing exceptions accross shared lib boundary
Date: Wed, 21 Aug 2002 09:35:00 -0000 [thread overview]
Message-ID: <200208211635.MAA22254@makai.watson.ibm.com> (raw)
In-Reply-To: <3D63C207.1060202@yahoo.co.uk>
>>>>> Abhijit H Bhosale writes:
Abhijit> I am working on AIX 4.3.3.0.
Abhijit> Using gcc version 2.95.3 20010315 (release).
Abhijit> I am facing problem in case of
Abhijit> throwing exceptions accross shared lib boundary.
Abhijit> I want to know whether gcc 2.95.3 supports this or not.
Abhijit> We tried with gcc version 3.0.4
Abhijit> It works only if we link the libstdc++ dynamically instead of static
Abhijit> linking.
Abhijit> Will the problem resolve by trying same thing with gcc - 2.95.3.
GCC 2.95.3 does not build libstdc++-v2 as a dynamic library. GCC
2.95.3 also uses setjmp/longjmp for exceptions while GCC 3 uses Dwarf2
information on AIX.
You should upgrade to GCC 3.2 or possibly use GCC from the AIX
Toolbox for Linux if you really need libstdc++-v2.
David
prev parent reply other threads:[~2002-08-21 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 9:29 Abhijit H. Bhosale
2002-08-21 9:35 ` David Edelsohn [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=200208211635.MAA22254@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=abhibhosale@yahoo.co.uk \
--cc=gcc@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).