public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: hb@gcc.x256.org
To: gcc-gnats@gcc.gnu.org
Subject: debug/8446: stabs generation crashes when class inherits from typedef struct
Date: Mon, 04 Nov 2002 02:36:00 -0000	[thread overview]
Message-ID: <20021104103438.17303.qmail@sources.redhat.com> (raw)


>Number:         8446
>Category:       debug
>Synopsis:       stabs generation crashes when class inherits from typedef struct
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Nov 04 02:36:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Nicholas Vinen
>Release:        3.2
>Organization:
>Environment:
i686-pc-linux-gnu (SuSE 7.3)
>Description:
The small file below causes GCC 3.2 to crash. It is because the STABS debug record generator can't handle classes which derive from typedef'd structs. Most other debug outputs can, and GCC compiles it fine. I am currently downloading the CVS version to see if it happens there too, but it isn't finished yet.
>How-To-Repeat:
g++ -gstabs test2.cc
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/plain; name="test2.cc"
Content-Disposition: inline; filename="test2.cc"


typedef struct
{
	int a;
} foo;

class bar : public foo
{
};

int main(void)
{
	return 0;
}


             reply	other threads:[~2002-11-04 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04  2:36 hb [this message]
2002-12-11 12:54 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=20021104103438.17303.qmail@sources.redhat.com \
    --to=hb@gcc.x256.org \
    --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).