From: David Carlton <carlton@kealia.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite] gdb.c++/classes.exp: add another ptype pattern
Date: Wed, 02 Jul 2003 15:52:00 -0000 [thread overview]
Message-ID: <yf2fzlpgc47.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <200307021539.h62FdJWR025063@duracef.shout.net> (Michael Elizabeth Chastain's message of "Wed, 2 Jul 2003 11:39:19 -0400")
On Wed, 2 Jul 2003 11:39:19 -0400, Michael Elizabeth Chastain
<mec@shout.net> said:
> # gcc 3.3 -gstabs+
> # gcc gcc-3_3-branch -gstabs+
> # gcc HEAD -gstabs+
> ptype obj_with_enum
> type = class ClassWithEnum {
> public:
> ClassWithEnum::PrivEnum priv_enum;
> int x;
> ClassWithEnum & operator=(ClassWithEnum const&);
> ClassWithEnum(ClassWithEnum const&);
> ClassWithEnum();
> }
> (gdb) FAIL: gdb.c++/classes.exp: ptype obj_with_enum
Sigh. Do the GCC stabs maintainers just randomly change their output
to keep us on our toes, or what? Maybe I shouldn't be annoyed, given
that that output is actually what we (eventually) _want_ GDB to be
producing, but if we want stabs debugging to work well, we need to sit
down and figure out what names stabs should list for various types,
and we need GCC to stick with whatever that decision might be.
I'm happy enough with your patch, but I'd prefer a comment at the
beginning of the test noting that it only passes by accident:
something like
# NOTE: carlton/2003-07-02: Currently, this test only passes with GCC
# 3.3 and higher and with -gstabs+, and it only passes in those
# situations by accident.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-07-02 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 15:39 Michael Elizabeth Chastain
2003-07-02 15:51 ` Daniel Jacobowitz
2003-07-02 15:52 ` David Carlton [this message]
2003-07-02 16:01 Michael Elizabeth Chastain
2003-07-02 16:09 Michael Elizabeth Chastain
2003-07-02 16:29 ` David Carlton
2003-07-02 16:38 ` Daniel Jacobowitz
2003-07-02 16:49 Michael Elizabeth Chastain
2003-07-02 17:07 ` David Carlton
2003-07-02 18:33 ` Daniel Jacobowitz
2003-07-02 19:02 ` Kevin Buettner
2003-07-02 19:19 ` David Carlton
2003-07-02 20:47 ` Kevin Buettner
2003-07-02 17:28 Michael Elizabeth Chastain
2003-07-02 19:11 Michael Elizabeth Chastain
2003-07-02 20:58 Michael Elizabeth Chastain
2003-07-02 21:33 Michael Elizabeth Chastain
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=yf2fzlpgc47.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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