From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@kealia.com
Cc: gdb@sources.redhat.com
Subject: Re: sunday project, gdb, 2003-09-26
Date: Mon, 29 Sep 2003 20:19:00 -0000 [thread overview]
Message-ID: <200309291829.h8TITkqv009816@duracef.shout.net> (raw)
mec> . gdb.cp/classes.exp: print (ClassWithEnum::PrivEnum) 42
mec> PASS -> KFAIL
mec> This is a regression in gdb. The KFAIL is:
mec> http://sources.redhat.com/gdb/bugs/826
mec> variables in C++ namespaces have to be enclosed in quotes
mec> This happened with gcc v3 -gstabs+.
dc> GCC 3.3, specifically: I don't see this with 3.2, where it's always
dc> been a KFAIL. The debug info for stabs changed from 3.2 to 3.3, I
dc> seem to recall.
Same here. It didn't regress for me with gcc 3.2-7-rh because
it was already KFAIL'ing with that.
dc> Right: at first, I was wondering why you called this a regression,
dc> given that it started out as a FAIL, but it really is the case that
dc> the new output is worse. (Is there anything wrong with the old
dc> output? It looks completely correct to me.)
I think the old output is correct and it's just a matter of upgrading
the test script to handle the many variations of 'ptype' output.
Actually we could use some more infrastructure for doing that.
Writing four to six 500-character regexp's for each ptype is
very fragile.
I'll make a "6.0 versus HEAD" regression report a little while after
gdb 6.0 is released.
Michael C
next reply other threads:[~2003-09-29 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 20:19 Michael Elizabeth Chastain [this message]
2003-09-29 19:54 ` David Carlton
2003-09-29 20:02 ` Daniel Jacobowitz
[not found] <200309272108.h8RL8LLA009276@duracef.shout.net>
2003-09-29 22:00 ` David Carlton
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=200309291829.h8TITkqv009816@duracef.shout.net \
--to=mec@shout.net \
--cc=carlton@kealia.com \
--cc=gdb@sources.redhat.com \
/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