This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[commit] Kfail "unknown output" test in print-threads.exp
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: gdb-patches at sources dot redhat dot com
- Date: Sun, 29 Jun 2003 15:32:57 -0400
- Subject: [commit] Kfail "unknown output" test in print-threads.exp
This is a longstanding problem in lin-lwp; I analyzed it on the lists some
months ago, and posted a patch which I later decided was too gross to
bother. Pending a better idea for fixing it, and in the interested of more
useful test results, I've checked in the below (HEAD and 6.0).
With this patch, on a lightly loaded i386-pc-linux-gnu system, all threads
tests pass. With load some of them still fail, but it appears to be a test
problem, and I'm not quite sure what to do about it.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2003-06-29 Daniel Jacobowitz <drow@mvista.com>
* gdb.threads/print-threads.exp (test_all_threads): Add kfail for
gdb/1265.
Index: gdb.threads/print-threads.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.threads/print-threads.exp,v
retrieving revision 1.3
diff -u -p -r1.3 print-threads.exp
--- gdb.threads/print-threads.exp 4 Jan 2003 23:05:05 -0000 1.3
+++ gdb.threads/print-threads.exp 29 Jun 2003 19:28:04 -0000
@@ -94,6 +94,13 @@ proc test_all_threads { name kill } {
fail "all threads ran once ($name) (total $i threads ran)"
}
}
+ -re "Program received signal SIGTRAP.*Thread \[0-9\]* \\(zombie\\).*$gdb_prompt $" {
+ if { $kill == 1 } {
+ kfail "gdb/1265" "Running threads ($name) (zombie thread)"
+ } else {
+ fail "Running threads ($name) (unknown output)"
+ }
+ }
-re "$gdb_prompt" {
fail "Running threads ($name) (unknown output)"
}