public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9597: Exception crash in shared library on Solaris 2.8 Intel platform
Date: Thu, 06 Feb 2003 16:26:00 -0000 [thread overview]
Message-ID: <20030206162601.11891.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/9597; it has been noted by GNATS.
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: pvantrepote@yahoo.fr
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/9597: Exception crash in shared library on Solaris 2.8 Intel platform
Date: Thu, 6 Feb 2003 17:16:57 +0100
On Thu, Feb 06, 2003 at 02:36:54PM -0000, pvantrepote@yahoo.fr wrote:
> I got a crash when i throw an exception in a shared library.
> I use gcc 3.2.1 on Solaris 2.8 i386 Intel Platform.
> [ ... ]
Core dumps with shared libs and Solaris rings a bell. However, what I
have in mind shouldn't apply to intel targets at all. Could you try the
following experiments and tell me if any of these help:
- Use the SUN supplied linker to create the shared library
- Add -z nocombreloc to the ld flags for the GNU linker
- link the shared lib statically into the program.
If any of these make a difference send the output of elfdump -G
for the shared lib.
regards Christian
--
THAT'S ALL FOLKS!
next reply other threads:[~2003-02-06 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 16:26 Christian Ehrhardt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 8:06 Pascal Vantrepote
2003-02-06 17:06 Pascal Vantrepote
2003-02-06 14:46 pvantrepote
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=20030206162601.11891.qmail@sources.redhat.com \
--to=ehrhardt@mathematik.uni-ulm.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).