From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@math.stanford.edu, fnasser@redhat.com
Cc: gdb@sources.redhat.com
Subject: Clean up gdb.c++ tests for dwarf 1
Date: Wed, 05 Feb 2003 21:30:00 -0000 [thread overview]
Message-ID: <200302052130.h15LUHB10715@duracef.shout.net> (raw)
gdb HEAD%20030205 has loads of this stuff in the C++ test suite:
setup_xfail_format "DWARF 1"
There are 81 instances of this.
Some test scripts have them, and some don't. I'd like to get rid
of them and replace them with something more coherent -- or nothing.
I see four choices.
(1) Just remove these calls to setup_xfail_format. If someone runs the
gdb test suite with DWARF 1, the test suite will do its job and give
FAIL results for all the C++ tests that do not work with DWARF 1.
(2) Change the tests so that each C++ test script reports a single
UNSUPPORTED for the whole script (if the debug format is DWARF 1).
This requires about five lines of code per script. This cannot be
centralized in 'skip_cplus_tests', because the check for the debug
format has to happen after the test script has compiled the test
program, started gdb, and proceeded to main, so that 'info source'
works.
(3) Leave the mess alone.
(4) Start fixing the DWARF 1 support. I'll start testing DWARF 1 and
filing bug reports for the things that don't work.
My preference order is (1) - (2) - (3) - (4).
What do you think?
Michael C
next reply other threads:[~2003-02-05 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 21:30 Michael Elizabeth Chastain [this message]
2003-02-05 21:37 ` David Carlton
2003-02-05 21:38 ` Jim Blandy
2003-02-05 21:43 ` Daniel Jacobowitz
2003-02-05 22:06 ` David Carlton
2003-02-05 22:18 ` Elena Zannoni
2003-02-05 22:41 Michael Elizabeth Chastain
2003-02-05 22:45 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=200302052130.h15LUHB10715@duracef.shout.net \
--to=mec@shout.net \
--cc=carlton@math.stanford.edu \
--cc=fnasser@redhat.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