public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	t6@pobox.com
Subject: Re: c++/7400: segfault with -shared option
Date: Wed, 30 Oct 2002 15:03:00 -0000	[thread overview]
Message-ID: <20021030230303.23530.qmail@sources.redhat.com> (raw)

Old Synopsis: dynamic_cast segfaults with -shared option
New Synopsis: segfault with -shared option

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Wed Oct 30 15:03:03 2002
State-Changed-Why:
    I see the same behavior, although it has nothing to do with
    dynamic_cast as suggested in the previous name of the 
    report: this also happens with this code:
    ------------------------------
    int main () {};
    ------------------------------
    
    Here's what I get:
    tmp/g> c++ x.cc
    tmp/g> ./a.out
    tmp/g>
    tmp/g> c++ -shared x.cc
    tmp/g> ./a.out
    Speicherzugriffsfehler
    (which means "Segmentation Fault", I just have not found
    out how to change the stupid german defaults on my system.)
    
    I guess I must be making something very naive, but then
    I don't see it, and this happens with 2.95, 3.2 and present
    CVS... :-(
    
    (And no, I don't have any idea why I can compile all my
    program with this option and why it runs. Also, the
    problem does not go away if I use -fPIC, or if I link
    separately. The crash happens before we get into "main",
    by the way, and we don't get a meaningful backtrace. Please
    someone enlighten me...)

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7400


             reply	other threads:[~2002-10-30 23:03 UTC|newest]

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

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=20021030230303.23530.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=t6@pobox.com \
    /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).