From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, jimb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Check for corruption of cv_type chain
Date: Fri, 03 May 2002 21:10:00 -0000 [thread overview]
Message-ID: <200205040410.g444AJn08545@duracef.shout.net> (raw)
Jim Blandy writes:
> [goes and checks his compilers] I see what's going on now. In GCC
> 2.96, -g doesn't get you `const' and `volatile' qualifiers in stabs
> --- that's why I thought -gstabs was the default. But in fact, GCC
> 2.96 won't give you those qualifiers no matter how nicely you ask.
Yes, you can see that happening here:
http://www.shout.net/~mec/sunday/2002-05-01/Attention-gdb-HEAD.html
Look at the lines for gdb.base/constvars.exp and gdb.base/volatile.exp.
gcc 2.95.3 -gstabs+ and gcc 2.96 -gstabs+ give many XFAIL's for these
tests.
> The current GCC sources default to Dwarf 2. So except for the
> window between the point where we taught dbxout.c to emit the
> qualifiers, and the point where we made Dwarf 2 the default (a pretty
> narrow window, in terms of installed base, no?), it doesn't matter
> whether -gstabs+ is the default or not; this test won't do its job
> with the default flags.
Two comments. First, gcc 3.0.4 falls into that window, and it is
the current released compiler. Indeed, every other gcc released in
the past twelve months or so has been a gcc 3.0.X compiler, so it
will have the cv qualifiers and have -gstabs+ as default. The window
is not narrow at all.
Second, the new tests are FAILing with gcc 2.95.3 -gstabs+ and
gcc 2.96-rh -gstabs+, the same way they fail with gcc 3.0.4 -gstabs+
and the other gcc 3-series compilers.
Let me pop open the logs:
# gcc 2.95.3 -gstabs+
(gdb) print var_in_b^M
FAIL: gdb.c++/hang.exp: doesn't overwrite struct type (timeout)
print var_in_hang3^M
FAIL: gdb.c++/hang.exp: doesn't corrupt cv_type chain (timeout)
testcase /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.c++/hang.exp
completed in 125 seconds
# gcc 2.96.3 -gstabs+
(gdb) file /berman/fsf/_today_/berman/test/gdb.c++/hang^M
Reading symbols from /berman/fsf/_today_/berman/test/gdb.c++/hang...done.^M
(gdb) print var_in_b^M
FAIL: gdb.c++/hang.exp: doesn't overwrite struct type (timeout)
print var_in_hang3^M
FAIL: gdb.c++/hang.exp: doesn't corrupt cv_type chain (timeout)
testcase /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.c++/hang.exp
completed in 126 seconds
The logs, executable files, and so on, are in the tarballs that I posted.
Michael C
next reply other threads:[~2002-05-04 4:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 21:10 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-03 19:37 Michael Elizabeth Chastain
2002-05-03 19:20 Michael Elizabeth Chastain
2002-05-03 17:54 Michael Elizabeth Chastain
2002-05-03 18:49 ` Daniel Jacobowitz
2002-05-03 17:33 Michael Elizabeth Chastain
2002-05-03 15:20 Michael Elizabeth Chastain
2002-05-03 17:28 ` Jim Blandy
2002-05-03 14:54 Jim Blandy
2002-05-03 15:14 ` Daniel Jacobowitz
2002-05-03 17:10 ` Jim Blandy
2002-05-03 17:25 ` Daniel Jacobowitz
2002-05-03 20:13 ` Jim Blandy
2002-05-03 18:44 ` Michael Snyder
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=200205040410.g444AJn08545@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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