public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dmonksfd@broadcom.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/7083: internal error (segfault) using -gstabs with dodgy class derivation
Date: Thu, 20 Jun 2002 03:46:00 -0000	[thread overview]
Message-ID: <20020620103048.18138.qmail@sources.redhat.com> (raw)


>Number:         7083
>Category:       c++
>Synopsis:       internal error (segfault) using -gstabs with dodgy class derivation
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 20 03:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     David Monksfield
>Release:        3.1
>Organization:
>Environment:

>Description:
gcc -v:
    Reading specs from /tools/gcc/3.1/i686-2.4.7-10/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
    Configured with: ../gcc-3.1/configure --prefix=/tools/gcc/3.1 --exec-prefix=/tools/gcc/3.1/i686-2.4.7-10 --disable-nls --enable-shared
    Thread model: single
    gcc version 3.1

Command line:
    g++ -gstabs -c gcc31bug.cc

Output:
    gcc31bug.cc:5: internal error: Segmentation fault
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

Preprocessed source:
    # 1 "gcc31bug.cc"
    # 1 "<built-in>"
    # 1 "<command line>"
    # 1 "gcc31bug.cc"
    typedef struct {
        int x;
    } A;

    class B: public A {
        int y;
    };

Notes:
    This is nasty (probably invalid) code, but it works
    under -ggdb, and probably shouldn't segfault anyway.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-06-20 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20  3:46 dmonksfd [this message]
2002-10-26  7:30 lerdsuwa

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=20020620103048.18138.qmail@sources.redhat.com \
    --to=dmonksfd@broadcom.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).