public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: David Jung <jungdl@ornl.gov>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7400: segfault with -shared option
Date: Thu, 31 Oct 2002 07:16:00 -0000	[thread overview]
Message-ID: <20021031151601.5694.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/7400; it has been noted by GNATS.

From: David Jung <jungdl@ornl.gov>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
   nobody@gcc.gnu.org, t6@pobox.com
Cc:  
Subject: Re: c++/7400: segfault with -shared option
Date: 31 Oct 2002 10:18:46 -0500

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view audit-trail
 
 Michael Matz <matz@suse.de> wrote:
 > Huh?  With -shared you create a shared library.  You can't run a shared
 > lib.  So getting a SEGV isn't wrong.
 
 Yep.  You're right.  My original problem was not in trying to
 run a shared lib, but in my effort to reduce the problem report
 to the minimum reproducible code, I obviously got a bit
 overzealous.  Sorry about that.
 I don't know if my original problem is fixed in 3.2, as the code
 was redesigned to eliminate the dynamic_casts that were causing
 the problem.
 So I guess you can close it.  If I come across it again I'll reopen
 or post another report.
 Thanks.
 
 


             reply	other threads:[~2002-10-31 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31  7:16 David Jung [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-30 15:46 Wolfgang Bangerth
2002-10-30 15:35 bangerth
2002-10-30 15:26 Michael Matz
2002-10-30 15:03 bangerth

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=20021031151601.5694.qmail@sources.redhat.com \
    --to=jungdl@ornl.gov \
    --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).