From: Ian Lance Taylor <ian@wasabisystems.com>
To: David Carlton <carlton@kealia.com>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: C++/Java regressions
Date: Tue, 25 Nov 2003 03:58:00 -0000 [thread overview]
Message-ID: <m3ekvx3xri.fsf@gossamer.airs.com> (raw)
In-Reply-To: <yf28ym5w7mg.fsf@hawaii.kealia.com>
David Carlton <carlton@kealia.com> writes:
> I did a CVS update on GDB for the first time in 4 days, and I got the
> following testsuite changes:
I ran the gdb testsuite both before and after the demangler changes,
and they appeared to make no significant difference. I enclose the
diff of gdb.sum. I've continued to run the gdb testsuite for each
significant demangler change.
I'm not saying that the problem is not the demangler. I don't know
what the problem is. If you can give more information, I would be
happy to adjust the demangler.
Ian
--- gdb.sum.hold Thu Nov 20 12:51:15 2003
+++ gdb.sum Sat Nov 22 11:15:26 2003
@@ -1,4 +1,4 @@
-Test Run By ian on Tue Nov 18 22:52:40 2003
+Test Run By ian on Sat Nov 22 11:10:33 2003
Native configuration is i686-pc-linux-gnu
=== gdb tests ===
@@ -2973,7 +2973,7 @@
PASS: gdb.base/page.exp: q
Running ../../../src/gdb/testsuite/gdb.base/pc-fp.exp ...
PASS: gdb.base/pc-fp.exp: get value of $pc (0x8048489)
-PASS: gdb.base/pc-fp.exp: get value of $fp (0xbfffe788)
+PASS: gdb.base/pc-fp.exp: get value of $fp (0xbfffe388)
PASS: gdb.base/pc-fp.exp: display/i $pc
PASS: gdb.base/pc-fp.exp: display/w $fp
Running ../../../src/gdb/testsuite/gdb.base/pointers.exp ...
@@ -5635,7 +5635,7 @@
PASS: gdb.cp/cplusfuncs.exp: print &'overload1arg(short)'
PASS: gdb.cp/cplusfuncs.exp: print &'overload1arg(unsigned short)'
PASS: gdb.cp/cplusfuncs.exp: print &'overload1arg(int)'
-PASS: gdb.cp/cplusfuncs.exp: print &'overload1arg(unsigned)'
+PASS: gdb.cp/cplusfuncs.exp: print &'overload1arg(unsigned int)'
PASS: gdb.cp/cplusfuncs.exp: print &'overload1arg(long)'
PASS: gdb.cp/cplusfuncs.exp: print &'overload1arg(unsigned long)'
PASS: gdb.cp/cplusfuncs.exp: print &'overload1arg(float)'
@@ -5697,9 +5697,9 @@
PASS: gdb.cp/cplusfuncs.exp: print &'hairyfunc2'
PASS: gdb.cp/cplusfuncs.exp: print &'hairyfunc3'
PASS: gdb.cp/cplusfuncs.exp: print &'hairyfunc4'
-KFAIL: gdb.cp/cplusfuncs.exp: print &'hairyfunc5' (PRMS: gdb/19)
-KFAIL: gdb.cp/cplusfuncs.exp: print &'hairyfunc6' (PRMS: gdb/19)
-KFAIL: gdb.cp/cplusfuncs.exp: print &'hairyfunc7' (PRMS: gdb/19)
+PASS: gdb.cp/cplusfuncs.exp: print &'hairyfunc5'
+PASS: gdb.cp/cplusfuncs.exp: print &'hairyfunc6'
+PASS: gdb.cp/cplusfuncs.exp: print &'hairyfunc7'
PASS: gdb.cp/cplusfuncs.exp: info function for "operator\*("
PASS: gdb.cp/cplusfuncs.exp: info function for "operator%("
PASS: gdb.cp/cplusfuncs.exp: info function for "operator-("
@@ -9473,11 +9473,11 @@
PASS: gdb.threads/print-threads.exp: Hit kill breakpoint, 7 (slow with kill breakpoint)
PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 3 (slow with kill breakpoint)
PASS: gdb.threads/print-threads.exp: Hit kill breakpoint, 8 (slow with kill breakpoint)
-PASS: gdb.threads/print-threads.exp: Hit kill breakpoint, 9 (slow with kill breakpoint)
PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 4 (slow with kill breakpoint)
+PASS: gdb.threads/print-threads.exp: Hit kill breakpoint, 9 (slow with kill breakpoint)
PASS: gdb.threads/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
PASS: gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
+PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
KFAIL: gdb.threads/print-threads.exp: Running threads (slow with kill breakpoint) (zombie thread) (PRMS: gdb/1265)
Running ../../../src/gdb/testsuite/gdb.threads/pthreads.exp ...
PASS: gdb.threads/pthreads.exp: successfully compiled posix threads test case
@@ -9516,8 +9516,7 @@
PASS: gdb.threads/pthreads.exp: check backtrace from thread 2
PASS: gdb.threads/pthreads.exp: apply backtrace command to all three threads
PASS: gdb.threads/pthreads.exp: set break at common_routine in thread 2
-PASS: gdb.threads/pthreads.exp: continue to bkpt at common_routine in thread 2
-PASS: gdb.threads/pthreads.exp: backtrace from thread 2 bkpt in common_routine
+FAIL: gdb.threads/pthreads.exp: continue to bkpt at common_routine in thread 2
Running ../../../src/gdb/testsuite/gdb.threads/schedlock.exp ...
PASS: gdb.threads/schedlock.exp: successfully compiled posix threads test case
PASS: gdb.threads/schedlock.exp: shell stty intr '^C'
@@ -9562,9 +9561,9 @@
PASS: gdb.threads/schedlock.exp: listed args (4)
PASS: gdb.threads/schedlock.exp: other thread 0 didn't run
PASS: gdb.threads/schedlock.exp: other thread 1 didn't run
-PASS: gdb.threads/schedlock.exp: other thread 2 didn't run
-PASS: gdb.threads/schedlock.exp: other thread 3 didn't run
PASS: gdb.threads/schedlock.exp: current thread ran
+PASS: gdb.threads/schedlock.exp: other thread 3 didn't run
+PASS: gdb.threads/schedlock.exp: other thread 4 didn't run
PASS: gdb.threads/schedlock.exp: other thread 5 didn't run
PASS: gdb.threads/schedlock.exp: step to increment (locked 0)
PASS: gdb.threads/schedlock.exp: step to increment (locked 1)
@@ -9581,9 +9580,9 @@
PASS: gdb.threads/schedlock.exp: listed args (5)
PASS: gdb.threads/schedlock.exp: other thread 0 didn't run (stepping)
PASS: gdb.threads/schedlock.exp: other thread 1 didn't run (stepping)
-PASS: gdb.threads/schedlock.exp: other thread 2 didn't run (stepping)
-PASS: gdb.threads/schedlock.exp: other thread 3 didn't run (stepping)
PASS: gdb.threads/schedlock.exp: current thread stepped locked
+PASS: gdb.threads/schedlock.exp: other thread 3 didn't run (stepping)
+PASS: gdb.threads/schedlock.exp: other thread 4 didn't run (stepping)
PASS: gdb.threads/schedlock.exp: other thread 5 didn't run (stepping)
Running ../../../src/gdb/testsuite/gdb.threads/step.exp ...
Running ../../../src/gdb/testsuite/gdb.threads/step2.exp ...
@@ -9736,11 +9735,11 @@
=== gdb Summary ===
-# of expected passes 8994
-# of unexpected failures 293
+# of expected passes 8995
+# of unexpected failures 294
# of unexpected successes 1
# of expected failures 71
-# of known failures 11
+# of known failures 8
# of unresolved testcases 20
# of untested testcases 6
# of unsupported tests 4
next prev parent reply other threads:[~2003-11-25 3:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 1:37 David Carlton
2003-11-25 1:48 ` The demangler was rewritten from scratch! Andrew Cagney
2003-11-25 3:58 ` Ian Lance Taylor [this message]
2003-11-26 4:04 ` C++/Java regressions Ian Lance Taylor
2003-11-26 15:32 ` Daniel Jacobowitz
2003-11-26 21:05 ` Ian Lance Taylor
2003-11-26 21:11 ` David Carlton
2003-11-26 21:12 ` Daniel Jacobowitz
2003-11-26 21:32 ` Ian Lance Taylor
2003-12-01 16:45 ` Daniel Jacobowitz
2003-11-30 2:57 ` Jim Blandy
2003-11-30 3:12 ` Daniel Jacobowitz
2003-11-25 4:44 Michael Elizabeth Chastain
2003-11-25 17:54 ` Ian Lance Taylor
2003-11-25 14:49 Michael Elizabeth Chastain
2003-11-25 15:06 ` Daniel Jacobowitz
2003-11-25 15:33 Michael Elizabeth Chastain
2003-11-25 17:06 Michael Elizabeth Chastain
2003-11-25 17:14 ` David Carlton
2003-11-25 17:59 ` Daniel Jacobowitz
2003-11-26 21:18 Michael Elizabeth Chastain
2003-11-26 21:33 ` Ian Lance Taylor
2003-11-26 21:44 Michael Elizabeth Chastain
2003-11-26 22:21 ` Ian Lance Taylor
2003-11-26 22:28 ` Daniel Jacobowitz
2003-11-26 22:34 ` Ian Lance Taylor
2003-11-26 22:48 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=m3ekvx3xri.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--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