public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jerrysiebe@mindspring.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/7788: g++-3.2 internal error: Segmentation fault
Date: Sat, 31 Aug 2002 01:06:00 -0000	[thread overview]
Message-ID: <20020831065950.8989.qmail@sources.redhat.com> (raw)


>Number:         7788
>Category:       c++
>Synopsis:       g++-3.2 internal error: Segmentation fault
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Aug 31 00:06:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     jerrysiebe@mindspring.com
>Release:        Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs  Configured with: ../gcc-3.2/configure  Thread model: posix  gcc version 3.2
>Organization:
>Environment:
GNU/Linux, Mandrake 8.2
Athlon XP 1800+
>Description:
foobar.cpp:3: internal error: Segmentation fault

class foo;
extern const foo bar;
class bar;  // kaBoom! :o

I think that says it all.  :)

The following versions don't exhibit this behaviour:
gcc version 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)
gcc version 3.0.4 (Mandrake Linux 8.2 3.0.4-2mdk)
gcc version 3.1 (Thread model: single, otherwise similar to my 3.2 build)
>How-To-Repeat:
g++ -c foobar.cpp
>Fix:

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

Y2xhc3MgZm9vOwpleHRlcm4gY29uc3QgZm9vIGJhcjsKY2xhc3MgYmFyOwo=


             reply	other threads:[~2002-08-31  7:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-31  1:06 jerrysiebe [this message]
2002-09-13 13:39 nathan
2002-09-29  2:16 Pop Sébastian
2002-09-29 10:44 nathan
2002-09-29 11:28 nathan
2002-09-29 11:56 Pop Sébastian

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=20020831065950.8989.qmail@sources.redhat.com \
    --to=jerrysiebe@mindspring.com \
    --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).