From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Current testsuite status
Date: Tue, 02 Apr 2002 17:43:00 -0000 [thread overview]
Message-ID: <20020402204353.A22418@nevyn.them.org> (raw)
In happy news, with today's posted patches and a few others, I have just
finished my best testsuite run ever on i386-linux/2.95.3/-gstabs+:
=== gdb Summary ===
# of expected passes 8302
# of unexpected successes 12
# of expected failures 168
That's right, no unexpected failures :)
The twelve expected failures are: Two from FLAG_PROTOTYPED, which I have an
attack plan for but am waiting for 5.2 to be released before I deal with;
five from C++ tests that should probably just be marked passing; one from a
C++ test that I suspect passes only by chance; one in gdb.base/return.exp
that should probably be a PASS; gdb.base/interrupt.exp, which I have
completely given up trying to understand (argh!!!!); and two from
constvars.exp, which should be passes since they don't involve any constness
information.
I'm probably going to pick another target/compiler/format combination and
try to do the same thing. If I take gcc3.0/DWARF-2, I'm going to have to do
an awful lot of C++ cleanup I've been putting off... perhaps PowerPC/2.95
first.
The patches:
<from Kevin, some weeks ago>
* thread-db.c (thread_db_wait): Don't attempt to use
lwp_from_thread(). Doing so assumes that the main thread
is already stopped and this might not be the case. Instead,
simply wait for any thread.
2002-04-02 Daniel Jacobowitz <drow@mvista.com>
* gdb.c++/classes.exp ("calling method for small class"): Match
updated register output.
2002-04-02 Daniel Jacobowitz <drow@mvista.com>
* gdb.c++/annota2.exp: Allow 2-4 "frames-invalid" markers.
2002-04-02 Daniel Jacobowitz <drow@mvista.com>
* config/i386/tm-linux.h: Define FILL_FPXREGSET.
* gregset.h: If FILL_FPXREGSET is defined, provide
gdb_fpxregset_t, supply_fpxregset, and fill_fpxregset.
* linux-proc.c (linux_do_thread_registers): If FILL_FPXREGSET
is defined, call fill_fpxregset.
2002-02-06 Jim Blandy <jimb@redhat.com>
Fix from Daniel Jacobowitz:
* config/i386/tm-linux.h (FRAME_CHAIN_VALID): Use
`func_frame_chain_valid' for this.
* i386-tdep.c (i386_gdbarch_init): Note that tm-linux.h is
overriding the selection we make here.
2002-04-02 Daniel Jacobowitz <drow@mvista.com>
Fix PR gdb/81
* breakpoint.c (bpstat_stop_status): Add ignore_breakpoints
argument. If ignore_breakpoints is nonzero, skip all
breakpoint-like events.
* breakpoint.h (bpstat_stop_status): Update prototype.
* infrun.c (handle_inferior_event): Update calls to
bpstat_stop_status. Call bpstat_stop_status even if
trap_expected.
2002-04-02 Daniel Jacobowitz <drow@mvista.com>
* jv-valprint (java_value_print): Limit read array elements by
print_max instead of printed arrray elements.
2002-04-01 Daniel Jacobowitz <drow@mvista.com>
* gdb.java/jmisc.java: Add ``void foo (String[] args)''. Call it.
* gdb.java/jmisc2.java: New test.
* gdb.java/jmisc.exp (ptype jmisc): Update to match ``foo''. Add
test for jmisc2.
2002-04-02 Daniel Jacobowitz <drow@mvista.com>
* linespec.c (decode_line_1): Check for a double quote after
a filename correctly.
2002-04-02 Daniel Jacobowitz <drow@mvista.com>
* gdb.mi/mi-console.exp: Accept native console output as an
XFAIL. Don't run the test if we don't have inferior IO.
* gdb.mi/mi0-console.exp: Likewise.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2002-04-03 1:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 17:43 Daniel Jacobowitz [this message]
2002-04-03 14:39 ` Kevin Buettner
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=20020402204353.A22418@nevyn.them.org \
--to=drow@mvista.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