public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7400: segfault with -shared option Date: Wed, 30 Oct 2002 15:26:00 -0000 [thread overview] Message-ID: <20021030232601.10926.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7400; it has been noted by GNATS. From: Michael Matz <matz@suse.de> To: <bangerth@dealii.org>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <t6@pobox.com>, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: c++/7400: segfault with -shared option Date: Thu, 31 Oct 2002 00:17:18 +0100 (CET) Hi, On 30 Oct 2002 bangerth@dealii.org wrote: > 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.) Huh? With -shared you create a shared library. You can't run a shared lib. So getting a SEGV isn't wrong. Ciao, Michael.
next reply other threads:[~2002-10-30 23:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-30 15:26 Michael Matz [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-31 7:16 David Jung 2002-10-30 15:46 Wolfgang Bangerth 2002-10-30 15:35 bangerth 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=20021030232601.10926.qmail@sources.redhat.com \ --to=matz@suse.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: linkBe 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).