public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: simon.patarin@inria.fr
To: gcc-gnats@gcc.gnu.org
Subject: c++/6855: g++ segfault
Date: Wed, 29 May 2002 02:02:00 -0000	[thread overview]
Message-ID: <20020529080230.30556.qmail@sources.redhat.com> (raw)


>Number:         6855
>Category:       c++
>Synopsis:       g++ segfault
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed May 29 01:06:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     g++
>Release:        3.1
>Organization:
>Environment:
Debian Linux unstable with stock 2.4.18 kernel
Reading specs from /usr/lib/gcc-lib/i386-linux/3.1/specs
Configured with: /mnt/data/gcc-3.1/gcc-3.1-3.1ds2/src/configure -v --enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr --mandir=$(prefix)/share/man --infodir=$(prefix)/share/info --with-gxx-include-dir=$(prefix)/include/g++-v3-3.1 --enable-shared --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --enable-clocale=gnu --enable-threads=posix --enable-java-gc=boehm --enable-objc-gc i386-linux
Thread model: posix
gcc version 3.1 (Debian)
>Description:
g++ segfaults with the one-liner source given as attachement
The only statement of the source is to initialize a global int variable in which there is call to abort():
int foo = (abort(), 0);
There is no such problem with g++ version 2.95.x
>How-To-Repeat:
g++-3.1 -c test.c
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="test.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="test.c"

I2luY2x1ZGUgPHN0ZGxpYi5oPgoKc3RhdGljIGludCBmb28gPSAoYWJvcnQoKSwgMCk7Cg==


             reply	other threads:[~2002-05-29  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29  2:02 simon.patarin [this message]
2002-05-31  8:06 jakub
2002-10-31 11:07 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=20020529080230.30556.qmail@sources.redhat.com \
    --to=simon.patarin@inria.fr \
    --cc=gcc-gnats@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).