GDB regressions

GDB regressions

[David Carlton]

I just did a CVS update, and I got a whole bunch of regressions.  I'll
include the diff of the gdb.sums after my signatures; these have all
appeared since Wednesday some time.

David Carlton
carlton@kealia.com

--- ../../testresults/11-12-03	2003-11-12 13:07:26.000000000 -0800
+++ testsuite/gdb.sum	2003-11-14 13:29:56.000000000 -0800
@@ -1,4 +1,4 @@
-Test Run By carlton on Wed Nov 12 12:19:13 2003
+Test Run By carlton on Fri Nov 14 13:14:43 2003
 Native configuration is i686-pc-linux-gnu
 
 		=== gdb tests ===
@@ -122,7 +122,7 @@
 PASS: gdb.base/annota1.exp: continue to printf
 XFAIL: gdb.base/annota1.exp: backtrace from shlibrary (PRMS 1270)
 XFAIL: gdb.base/annota1.exp: send SIGUSR1 (PRMS 1270)
-PASS: gdb.base/annota1.exp: backtrace @ signal handler
+FAIL: gdb.base/annota1.exp: backtrace @ signal handler
 PASS: gdb.base/annota1.exp: delete bp 1
 PASS: gdb.base/annota1.exp: delete bp 2
 PASS: gdb.base/annota1.exp: delete bp 3
@@ -148,7 +148,7 @@
 PASS: gdb.base/annota3.exp: continue to printf
 PASS: gdb.base/annota3.exp: backtrace from shlibrary
 PASS: gdb.base/annota3.exp: send SIGUSR1
-PASS: gdb.base/annota3.exp: backtrace @ signal handler
+FAIL: gdb.base/annota3.exp: backtrace @ signal handler (pattern 2)
 PASS: gdb.base/annota3.exp: delete bp 1
 PASS: gdb.base/annota3.exp: delete bp 2
 PASS: gdb.base/annota3.exp: delete bp 3
@@ -2973,7 +2973,7 @@
 PASS: gdb.base/page.exp: q
 Running ./gdb.base/pc-fp.exp ...
 PASS: gdb.base/pc-fp.exp: get value of $pc (0x804838a)
-PASS: gdb.base/pc-fp.exp: get value of $fp (0xbfffea88)
+PASS: gdb.base/pc-fp.exp: get value of $fp (0xbfffd808)
 PASS: gdb.base/pc-fp.exp: display/i $pc
 PASS: gdb.base/pc-fp.exp: display/w $fp
 Running ./gdb.base/pointers.exp ...
@@ -4276,7 +4276,7 @@
 PASS: gdb.base/selftest.exp: Set xgdb prompt
 PASS: gdb.base/selftest.exp: send ^C to child process
 PASS: gdb.base/selftest.exp: send SIGINT signal to child process
-PASS: gdb.base/selftest.exp: backtrace through signal handler
+FAIL: gdb.base/selftest.exp: backtrace through signal handler
 Running ./gdb.base/setshow.exp ...
 PASS: gdb.base/setshow.exp: default annotation_level is zero
 PASS: gdb.base/setshow.exp: set annotate 2
@@ -4902,7 +4902,7 @@
 PASS: gdb.base/signals.exp: break handler
 PASS: gdb.base/signals.exp: next to 2nd ++count in signals_tests_1
 PASS: gdb.base/signals.exp: next to handler in signals_tests_1
-PASS: gdb.base/signals.exp: backtrace in signals_tests_1
+FAIL: gdb.base/signals.exp: backtrace in signals_tests_1
 PASS: gdb.base/signals.exp: break func1
 PASS: gdb.base/signals.exp: break func2
 XFAIL: gdb.base/signals.exp: continue to func1 (probably kernel bug)
@@ -4924,7 +4924,7 @@
 PASS: gdb.base/signals.exp: next to alarm #2 in signals.exp
 PASS: gdb.base/signals.exp: next to ++count #2 in signals.exp
 PASS: gdb.base/signals.exp: p func1 () #2 in signals.exp
-PASS: gdb.base/signals.exp: bt in signals.exp
+FAIL: gdb.base/signals.exp: bt in signals.exp
 PASS: gdb.base/signals.exp: continue in signals.exp
 PASS: gdb.base/signals.exp: p count #2 in signals.exp
 PASS: gdb.base/signals.exp: info signals
@@ -7625,17 +7625,19 @@
 Running ./gdb.java/jmisc1.exp ...
 PASS: gdb.java/jmisc1.exp: set print sevenbit-strings
 PASS: gdb.java/jmisc1.exp: set language to "java"
+FAIL: gdb.java/jmisc1.exp: running to jmisc.main(java.lang.String[]) in runto
 FAIL: gdb.java/jmisc1.exp: ptype jmisc
-PASS: gdb.java/jmisc1.exp: p args
-PASS: gdb.java/jmisc1.exp: p *args
+FAIL: gdb.java/jmisc1.exp: p args
+FAIL: gdb.java/jmisc1.exp: p *args
 PASS: gdb.java/jmisc1.exp: break exit
-PASS: gdb.java/jmisc1.exp: continue to exit
+FAIL: gdb.java/jmisc1.exp: continue to exit
 Running ./gdb.java/jmisc2.exp ...
 PASS: gdb.java/jmisc2.exp: set print sevenbit-strings
 PASS: gdb.java/jmisc2.exp: set language to "java"
 FAIL: gdb.java/jmisc2.exp: ptype jmisc
-PASS: gdb.java/jmisc2.exp: p args
-PASS: gdb.java/jmisc2.exp: p *args
+FAIL: gdb.java/jmisc2.exp: running to jmisc.main(java.lang.String[]) in runto
+FAIL: gdb.java/jmisc2.exp: p args
+FAIL: gdb.java/jmisc2.exp: p *args
 Running ./gdb.java/jv-exp.exp ...
 PASS: gdb.java/jv-exp.exp: set print sevenbit-strings
 PASS: gdb.java/jv-exp.exp: set width 0
@@ -7691,53 +7693,53 @@
 PASS: gdb.mi/gdb669.exp: successfully compiled posix threads test case
 PASS: gdb.mi/gdb669.exp: breakpoint at main
 PASS: gdb.mi/gdb669.exp: mi runto main
-PASS: gdb.mi/gdb669.exp: -thread-list-ids (at main)
-PASS: gdb.mi/gdb669.exp: info threads (at main)
+FAIL: gdb.mi/gdb669.exp: -thread-list-ids (at main)
+FAIL: gdb.mi/gdb669.exp: info threads (at main)
 PASS: gdb.mi/gdb669.exp: finding MI result string (at main)
 PASS: gdb.mi/gdb669.exp: finding number of threads in MI output (at main)
 PASS: gdb.mi/gdb669.exp: got number of threads from MI (at main)
 PASS: gdb.mi/gdb669.exp: console and MI have same number of threads (at main)
-PASS: gdb.mi/gdb669.exp: -thread_list_ids (at main)
+FAIL: gdb.mi/gdb669.exp: -thread_list_ids (at main)
 PASS: gdb.mi/gdb669.exp: finding threads in MI output (at main)
 PASS: gdb.mi/gdb669.exp: MI and console have same threads (at main)
 PASS: gdb.mi/gdb669.exp: next, try 0
-PASS: gdb.mi/gdb669.exp: -thread-list-ids (try 0)
-PASS: gdb.mi/gdb669.exp: info threads (try 0)
+FAIL: gdb.mi/gdb669.exp: -thread-list-ids (try 0)
+FAIL: gdb.mi/gdb669.exp: info threads (try 0)
 PASS: gdb.mi/gdb669.exp: finding MI result string (try 0)
 PASS: gdb.mi/gdb669.exp: finding number of threads in MI output (try 0)
 PASS: gdb.mi/gdb669.exp: got number of threads from MI (try 0)
 PASS: gdb.mi/gdb669.exp: console and MI have same number of threads (try 0)
-PASS: gdb.mi/gdb669.exp: -thread_list_ids (try 0)
+FAIL: gdb.mi/gdb669.exp: -thread_list_ids (try 0)
 PASS: gdb.mi/gdb669.exp: finding threads in MI output (try 0)
 PASS: gdb.mi/gdb669.exp: MI and console have same threads (try 0)
-PASS: gdb.mi/gdb669.exp: next, try 1
-PASS: gdb.mi/gdb669.exp: -thread-list-ids (try 1)
-PASS: gdb.mi/gdb669.exp: info threads (try 1)
+FAIL: gdb.mi/gdb669.exp: next, try 1 (unknown output after running)
+FAIL: gdb.mi/gdb669.exp: -thread-list-ids (try 1)
+FAIL: gdb.mi/gdb669.exp: info threads (try 1)
 PASS: gdb.mi/gdb669.exp: finding MI result string (try 1)
 PASS: gdb.mi/gdb669.exp: finding number of threads in MI output (try 1)
 PASS: gdb.mi/gdb669.exp: got number of threads from MI (try 1)
 PASS: gdb.mi/gdb669.exp: console and MI have same number of threads (try 1)
-PASS: gdb.mi/gdb669.exp: -thread_list_ids (try 1)
+FAIL: gdb.mi/gdb669.exp: -thread_list_ids (try 1)
 PASS: gdb.mi/gdb669.exp: finding threads in MI output (try 1)
 PASS: gdb.mi/gdb669.exp: MI and console have same threads (try 1)
-PASS: gdb.mi/gdb669.exp: next, try 2
-PASS: gdb.mi/gdb669.exp: -thread-list-ids (try 2)
-PASS: gdb.mi/gdb669.exp: info threads (try 2)
+FAIL: gdb.mi/gdb669.exp: next, try 2 (unknown output after running)
+FAIL: gdb.mi/gdb669.exp: -thread-list-ids (try 2)
+FAIL: gdb.mi/gdb669.exp: info threads (try 2)
 PASS: gdb.mi/gdb669.exp: finding MI result string (try 2)
 PASS: gdb.mi/gdb669.exp: finding number of threads in MI output (try 2)
 PASS: gdb.mi/gdb669.exp: got number of threads from MI (try 2)
 PASS: gdb.mi/gdb669.exp: console and MI have same number of threads (try 2)
-PASS: gdb.mi/gdb669.exp: -thread_list_ids (try 2)
+FAIL: gdb.mi/gdb669.exp: -thread_list_ids (try 2)
 PASS: gdb.mi/gdb669.exp: finding threads in MI output (try 2)
 PASS: gdb.mi/gdb669.exp: MI and console have same threads (try 2)
 PASS: gdb.mi/gdb669.exp: next, try 3
-PASS: gdb.mi/gdb669.exp: -thread-list-ids (try 3)
-PASS: gdb.mi/gdb669.exp: info threads (try 3)
+FAIL: gdb.mi/gdb669.exp: -thread-list-ids (try 3)
+FAIL: gdb.mi/gdb669.exp: info threads (try 3)
 PASS: gdb.mi/gdb669.exp: finding MI result string (try 3)
 PASS: gdb.mi/gdb669.exp: finding number of threads in MI output (try 3)
 PASS: gdb.mi/gdb669.exp: got number of threads from MI (try 3)
 PASS: gdb.mi/gdb669.exp: console and MI have same number of threads (try 3)
-PASS: gdb.mi/gdb669.exp: -thread_list_ids (try 3)
+FAIL: gdb.mi/gdb669.exp: -thread_list_ids (try 3)
 PASS: gdb.mi/gdb669.exp: finding threads in MI output (try 3)
 PASS: gdb.mi/gdb669.exp: MI and console have same threads (try 3)
 Running ./gdb.mi/gdb680.exp ...
@@ -7862,18 +7864,11 @@
 Running ./gdb.mi/mi-pthreads.exp ...
 PASS: gdb.mi/mi-pthreads.exp: successfully compiled posix threads test case
 PASS: gdb.mi/mi-pthreads.exp: breakpoint at done_making_threads
-PASS: gdb.mi/mi-pthreads.exp: mi runto done_making_threads
-PASS: gdb.mi/mi-pthreads.exp: -thread_list_ids (in check_mi_thread_command_set)
+FAIL: gdb.mi/mi-pthreads.exp: mi runto done_making_threads (2)
+FAIL: gdb.mi/mi-pthreads.exp: -thread_list_ids (in check_mi_thread_command_set)
 PASS: gdb.mi/mi-pthreads.exp: finding threads in MI output (in check_mi_thread_command_set)
 PASS: gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select
 PASS: gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 123456789
-PASS: gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 7
-PASS: gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 6
-PASS: gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 5
-PASS: gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 4
-PASS: gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 3
-PASS: gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 2
-PASS: gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 1
 Running ./gdb.mi/mi-read-memory.exp ...
 PASS: gdb.mi/mi-read-memory.exp: breakpoint at main
 PASS: gdb.mi/mi-read-memory.exp: mi runto main
@@ -7947,7 +7942,7 @@
 PASS: gdb.mi/mi-syn-frame.exp: 404-stack-list-frames 0 0
 PASS: gdb.mi/mi-syn-frame.exp: 405-break-insert subroutine
 PASS: gdb.mi/mi-syn-frame.exp: 406-data-evaluate-expression have_a_very_merry_interrupt()
-PASS: gdb.mi/mi-syn-frame.exp: 407-stack-list-frames
+FAIL: gdb.mi/mi-syn-frame.exp: 407-stack-list-frames
 PASS: gdb.mi/mi-syn-frame.exp: 408-exec-continue
 PASS: gdb.mi/mi-syn-frame.exp: 409-stack-list-frames 0 0
 PASS: gdb.mi/mi-syn-frame.exp: call inferior function which raises exception
@@ -8435,18 +8430,11 @@
 Running ./gdb.mi/mi1-pthreads.exp ...
 PASS: gdb.mi/mi1-pthreads.exp: successfully compiled posix threads test case
 PASS: gdb.mi/mi1-pthreads.exp: breakpoint at done_making_threads
-PASS: gdb.mi/mi1-pthreads.exp: mi runto done_making_threads
-PASS: gdb.mi/mi1-pthreads.exp: -thread_list_ids (in check_mi_thread_command_set)
+FAIL: gdb.mi/mi1-pthreads.exp: mi runto done_making_threads (2)
+FAIL: gdb.mi/mi1-pthreads.exp: -thread_list_ids (in check_mi_thread_command_set)
 PASS: gdb.mi/mi1-pthreads.exp: finding threads in MI output (in check_mi_thread_command_set)
 PASS: gdb.mi/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select
 PASS: gdb.mi/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select 123456789
-PASS: gdb.mi/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select 7
-PASS: gdb.mi/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select 6
-PASS: gdb.mi/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select 5
-PASS: gdb.mi/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select 4
-PASS: gdb.mi/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select 3
-PASS: gdb.mi/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select 2
-PASS: gdb.mi/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select 1
 Running ./gdb.mi/mi1-read-memory.exp ...
 PASS: gdb.mi/mi1-read-memory.exp: breakpoint at main
 PASS: gdb.mi/mi1-read-memory.exp: mi runto main
@@ -9032,18 +9020,11 @@
 Running ./gdb.mi/mi2-pthreads.exp ...
 PASS: gdb.mi/mi2-pthreads.exp: successfully compiled posix threads test case
 PASS: gdb.mi/mi2-pthreads.exp: breakpoint at done_making_threads
-PASS: gdb.mi/mi2-pthreads.exp: mi runto done_making_threads
-PASS: gdb.mi/mi2-pthreads.exp: -thread_list_ids (in check_mi_thread_command_set)
+FAIL: gdb.mi/mi2-pthreads.exp: mi runto done_making_threads (2)
+FAIL: gdb.mi/mi2-pthreads.exp: -thread_list_ids (in check_mi_thread_command_set)
 PASS: gdb.mi/mi2-pthreads.exp: finding threads in MI output (in check_mi_thread_command_set)
 PASS: gdb.mi/mi2-pthreads.exp: check_mi_thread_command_set: -thread-select
 PASS: gdb.mi/mi2-pthreads.exp: check_mi_thread_command_set: -thread-select 123456789
-PASS: gdb.mi/mi2-pthreads.exp: check_mi_thread_command_set: -thread-select 7
-PASS: gdb.mi/mi2-pthreads.exp: check_mi_thread_command_set: -thread-select 6
-PASS: gdb.mi/mi2-pthreads.exp: check_mi_thread_command_set: -thread-select 5
-PASS: gdb.mi/mi2-pthreads.exp: check_mi_thread_command_set: -thread-select 4
-PASS: gdb.mi/mi2-pthreads.exp: check_mi_thread_command_set: -thread-select 3
-PASS: gdb.mi/mi2-pthreads.exp: check_mi_thread_command_set: -thread-select 2
-PASS: gdb.mi/mi2-pthreads.exp: check_mi_thread_command_set: -thread-select 1
 Running ./gdb.mi/mi2-read-memory.exp ...
 PASS: gdb.mi/mi2-read-memory.exp: breakpoint at main
 PASS: gdb.mi/mi2-read-memory.exp: mi runto main
@@ -9117,7 +9098,7 @@
 PASS: gdb.mi/mi2-syn-frame.exp: 404-stack-list-frames 0 0
 PASS: gdb.mi/mi2-syn-frame.exp: 405-break-insert subroutine
 PASS: gdb.mi/mi2-syn-frame.exp: 406-data-evaluate-expression have_a_very_merry_interrupt()
-PASS: gdb.mi/mi2-syn-frame.exp: 407-stack-list-frames
+FAIL: gdb.mi/mi2-syn-frame.exp: 407-stack-list-frames
 PASS: gdb.mi/mi2-syn-frame.exp: 408-exec-continue
 PASS: gdb.mi/mi2-syn-frame.exp: 409-stack-list-frames 0 0
 PASS: gdb.mi/mi2-syn-frame.exp: call inferior function which raises exception
@@ -9766,13 +9747,7 @@
 Running ./gdb.threads/gcore-thread.exp ...
 PASS: gdb.threads/gcore-thread.exp: successfully compiled posix threads test case
 PASS: gdb.threads/gcore-thread.exp: help gcore
-PASS: gdb.threads/gcore-thread.exp: thread 1 is running
-PASS: gdb.threads/gcore-thread.exp: thread 2 is running
-PASS: gdb.threads/gcore-thread.exp: save a corefile
-PASS: gdb.threads/gcore-thread.exp: re-load generated corefile
-PASS: gdb.threads/gcore-thread.exp: corefile contains at least two threads
-PASS: gdb.threads/gcore-thread.exp: a corefile thread is executing thread2
-PASS: gdb.threads/gcore-thread.exp: thread2 is current thread in corefile
+UNSUPPORTED: gdb.threads/gcore-thread.exp: gdb does not support threads on this target
 Running ./gdb.threads/killed.exp ...
 PASS: gdb.threads/killed.exp: successfully compiled posix threads test case
 PASS: gdb.threads/killed.exp: run program to completion
@@ -9780,46 +9755,7 @@
 Running ./gdb.threads/linux-dp.exp ...
 PASS: gdb.threads/linux-dp.exp: info threads 1
 PASS: gdb.threads/linux-dp.exp: continue to breakpoint: about to create philosopher: 0
-PASS: gdb.threads/linux-dp.exp: create philosopher: 0
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: about to create philosopher: 1
-PASS: gdb.threads/linux-dp.exp: create philosopher: 1
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: about to create philosopher: 2
-PASS: gdb.threads/linux-dp.exp: create philosopher: 2
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: about to create philosopher: 3
-PASS: gdb.threads/linux-dp.exp: create philosopher: 3
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: about to create philosopher: 4
-PASS: gdb.threads/linux-dp.exp: create philosopher: 4
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: main thread's sleep
-PASS: gdb.threads/linux-dp.exp: info threads 2
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print
-PASS: gdb.threads/linux-dp.exp: first thread-specific breakpoint hit
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print, pass: 0
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print, pass: 1
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print, pass: 2
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print, pass: 3
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print, pass: 4
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print, pass: 5
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print, pass: 6
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print, pass: 7
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print, pass: 8
-PASS: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print, pass: 9
-PASS: gdb.threads/linux-dp.exp: thread-specific breakpoint is thread-specific
-PASS: gdb.threads/linux-dp.exp: selected thread: 1
-FAIL: gdb.threads/linux-dp.exp: philosopher is distinct: 1
-PASS: gdb.threads/linux-dp.exp: selected thread: 2
-PASS: gdb.threads/linux-dp.exp: manager thread is distinct: 2
-PASS: gdb.threads/linux-dp.exp: selected thread: 3
-PASS: gdb.threads/linux-dp.exp: philosopher is distinct: 3
-PASS: gdb.threads/linux-dp.exp: selected thread: 4
-PASS: gdb.threads/linux-dp.exp: philosopher is distinct: 4
-PASS: gdb.threads/linux-dp.exp: selected thread: 5
-PASS: gdb.threads/linux-dp.exp: philosopher is distinct: 5
-PASS: gdb.threads/linux-dp.exp: selected thread: 6
-PASS: gdb.threads/linux-dp.exp: philosopher is distinct: 6
-PASS: gdb.threads/linux-dp.exp: selected thread: 7
-PASS: gdb.threads/linux-dp.exp: philosopher is distinct: 7
-PASS: gdb.threads/linux-dp.exp: found an interesting thread
-PASS: gdb.threads/linux-dp.exp: manager thread found (not found) when expected
+UNSUPPORTED: gdb.threads/linux-dp.exp: This GDB does not support threads on this system.
 Running ./gdb.threads/print-threads.exp ...
 PASS: gdb.threads/print-threads.exp: successfully compiled posix threads test case
 PASS: gdb.threads/print-threads.exp: set print sevenbit-strings
@@ -9827,154 +9763,32 @@
 PASS: gdb.threads/print-threads.exp: shell stty intr '^C'
 PASS: gdb.threads/print-threads.exp: break thread_function
 PASS: gdb.threads/print-threads.exp: set var slow = 0
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 1 (fast)
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 2 (fast)
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 3 (fast)
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 4 (fast)
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (fast)
-PASS: gdb.threads/print-threads.exp: program exited normally
-PASS: gdb.threads/print-threads.exp: all threads ran once (fast)
+FAIL: gdb.threads/print-threads.exp: Running threads (fast) (unknown output)
 PASS: gdb.threads/print-threads.exp: break thread_function (2)
 PASS: gdb.threads/print-threads.exp: set var slow = 1
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 1 (slow)
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 2 (slow)
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 3 (slow)
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 4 (slow)
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow)
-PASS: gdb.threads/print-threads.exp: program exited normally
-PASS: gdb.threads/print-threads.exp: all threads ran once (slow)
+FAIL: gdb.threads/print-threads.exp: Running threads (slow) (unknown output)
 PASS: gdb.threads/print-threads.exp: break thread_function (3)
 PASS: gdb.threads/print-threads.exp: set var slow = 1 (2)
 PASS: gdb.threads/print-threads.exp: break kill
-PASS: gdb.threads/print-threads.exp: Hit kill breakpoint, 1 (slow with kill breakpoint)
-PASS: gdb.threads/print-threads.exp: Hit kill breakpoint, 2 (slow with kill breakpoint)
-PASS: gdb.threads/print-threads.exp: Hit kill breakpoint, 3 (slow with kill breakpoint)
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 1 (slow with kill breakpoint)
-PASS: gdb.threads/print-threads.exp: Hit kill breakpoint, 4 (slow with kill breakpoint)
-PASS: gdb.threads/print-threads.exp: Hit kill breakpoint, 5 (slow with kill breakpoint)
-PASS: gdb.threads/print-threads.exp: Hit thread_function breakpoint, 2 (slow with kill breakpoint)
-PASS: gdb.threads/print-threads.exp: Hit kill breakpoint, 6 (slow with kill breakpoint)
-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, 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)
-KFAIL: gdb.threads/print-threads.exp: Running threads (slow with kill breakpoint) (zombie thread) (PRMS: gdb/1265)
+FAIL: gdb.threads/print-threads.exp: Running threads (slow with kill breakpoint) (timeout)
 Running ./gdb.threads/pthreads.exp ...
 PASS: gdb.threads/pthreads.exp: successfully compiled posix threads test case
 PASS: gdb.threads/pthreads.exp: set print sevenbit-strings
 PASS: gdb.threads/pthreads.exp: set width 0
 PASS: gdb.threads/pthreads.exp: shell stty intr '^C'
-PASS: gdb.threads/pthreads.exp: info threads
-PASS: gdb.threads/pthreads.exp: break thread1
-PASS: gdb.threads/pthreads.exp: Continue to creation of first thread
-PASS: gdb.threads/pthreads.exp: disable
-PASS: gdb.threads/pthreads.exp: break thread2
-PASS: gdb.threads/pthreads.exp: Continue to creation of second thread
-PASS: gdb.threads/pthreads.exp: set var common_routine::hits=0
-PASS: gdb.threads/pthreads.exp: set var common_routine::from_thread1=0
-PASS: gdb.threads/pthreads.exp: set var common_routine::from_thread2=0
-PASS: gdb.threads/pthreads.exp: set var common_routine::from_main=0
-PASS: gdb.threads/pthreads.exp: set var common_routine::full_coverage=0
-PASS: gdb.threads/pthreads.exp: disable
-PASS: gdb.threads/pthreads.exp: tbreak common_routine if hits >= 15
-PASS: gdb.threads/pthreads.exp: stopped before calling common_routine 15 times
-PASS: gdb.threads/pthreads.exp: All threads running after startup
-PASS: gdb.threads/pthreads.exp: Continue with all threads running
-PASS: gdb.threads/pthreads.exp: Stopped with a ^C
-PASS: gdb.threads/pthreads.exp: bt
-PASS: gdb.threads/pthreads.exp: set var common_routine::hits=0
-PASS: gdb.threads/pthreads.exp: set var common_routine::from_thread1=0
-PASS: gdb.threads/pthreads.exp: set var common_routine::from_thread2=0
-PASS: gdb.threads/pthreads.exp: set var common_routine::from_main=0
-PASS: gdb.threads/pthreads.exp: set var common_routine::full_coverage=0
-PASS: gdb.threads/pthreads.exp: disable
-PASS: gdb.threads/pthreads.exp: tbreak common_routine if hits >= 15
-PASS: gdb.threads/pthreads.exp: stopped before calling common_routine 15 times
-PASS: gdb.threads/pthreads.exp: All threads running after continuing from ^C stop
-FAIL: gdb.threads/pthreads.exp: check backtrace from main thread
-PASS: gdb.threads/pthreads.exp: check backtrace from thread 1
-PASS: gdb.threads/pthreads.exp: check backtrace from thread 2
-FAIL: 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
+UNSUPPORTED: gdb.threads/pthreads.exp: gdb does not support pthreads for this machine
 Running ./gdb.threads/step.exp ...
 Running ./gdb.threads/step2.exp ...
 Running ./gdb.threads/switch-threads.exp ...
 PASS: gdb.threads/switch-threads.exp: successfully compiled posix threads test case
-PASS: gdb.threads/switch-threads.exp: continue to breakpoint: continue to thread_func
-PASS: gdb.threads/switch-threads.exp: next
+FAIL: gdb.threads/switch-threads.exp: continue to breakpoint: continue to thread_func
+FAIL: gdb.threads/switch-threads.exp: next
 Running ./gdb.threads/tls-shared.exp ...
 PASS: gdb.threads/tls-shared.exp: successfully compiled posix threads test case
 PASS: gdb.threads/tls-shared.exp: successfully compiled posix threads test case
@@ -9984,64 +9798,36 @@
 PASS: gdb.threads/tls.exp: set breakpoint at all threads
 PASS: gdb.threads/tls.exp: set breakpoint at synch point
 PASS: gdb.threads/tls.exp: set breakpoint at exit
-PASS: gdb.threads/tls.exp: continue to first thread: get to thread
-PASS: gdb.threads/tls.exp: at least one th in spin while stopped at first th
-PASS: gdb.threads/tls.exp: first thread print me
+FAIL: gdb.threads/tls.exp: continue to first thread: no progress?
+FAIL: gdb.threads/tls.exp: at least one th in spin while stopped at first th
+FAIL: gdb.threads/tls.exp: first thread print me
 FAIL: gdb.threads/tls.exp: first thread local storage
 FAIL: gdb.threads/tls.exp: first another thread local storage
 FAIL: gdb.threads/tls.exp: first info address a_thread_local
 FAIL: gdb.threads/tls.exp: first info address another_thread_local
-PASS: gdb.threads/tls.exp: continue to second thread
-PASS: gdb.threads/tls.exp: at least one th in spin while stopped at second th
-PASS: gdb.threads/tls.exp: second thread print me
+FAIL: gdb.threads/tls.exp: continue to second thread
+FAIL: gdb.threads/tls.exp: at least one th in spin while stopped at second th
+FAIL: gdb.threads/tls.exp: second thread print me
 FAIL: gdb.threads/tls.exp: second thread local storage
 FAIL: gdb.threads/tls.exp: second another thread local storage
 FAIL: gdb.threads/tls.exp: second info address a_thread_local
 FAIL: gdb.threads/tls.exp: second info address another_thread_local
-PASS: gdb.threads/tls.exp: continue to third thread
-PASS: gdb.threads/tls.exp: at least one th in spin while stopped at third th
-PASS: gdb.threads/tls.exp: third thread print me
-FAIL: gdb.threads/tls.exp: third thread local storage
-FAIL: gdb.threads/tls.exp: third another thread local storage
-FAIL: gdb.threads/tls.exp: third info address a_thread_local
-FAIL: gdb.threads/tls.exp: third info address another_thread_local
-PASS: gdb.threads/tls.exp: continue to synch point
-PASS: gdb.threads/tls.exp: get number of threads
-PASS: gdb.threads/tls.exp: selected thread: 1
-PASS: gdb.threads/tls.exp: backtrace of thread number 1 not relevant
-PASS: gdb.threads/tls.exp: selected thread: 2
-PASS: gdb.threads/tls.exp: backtrace of thread number 2 not relevant
-PASS: gdb.threads/tls.exp: selected thread: 3
-PASS: gdb.threads/tls.exp: backtrace of thread number 3 in spin
-PASS: gdb.threads/tls.exp: selected thread: 4
-PASS: gdb.threads/tls.exp: backtrace of thread number 4 in spin
-PASS: gdb.threads/tls.exp: selected thread: 5
-PASS: gdb.threads/tls.exp: backtrace of thread number 5 in spin
-PASS: gdb.threads/tls.exp: selected thread: 4
-PASS: gdb.threads/tls.exp: thread 4 up
-PASS: gdb.threads/tls.exp: 4 thread print me
-FAIL: gdb.threads/tls.exp: 4 thread local storage
-FAIL: gdb.threads/tls.exp: 4 another thread local storage
-FAIL: gdb.threads/tls.exp: 4 info address a_thread_local
-FAIL: gdb.threads/tls.exp: 4 info address another_thread_local
-PASS: gdb.threads/tls.exp: selected thread: 5
-PASS: gdb.threads/tls.exp: thread 5 up
-PASS: gdb.threads/tls.exp: 5 thread print me
-FAIL: gdb.threads/tls.exp: 5 thread local storage
-FAIL: gdb.threads/tls.exp: 5 another thread local storage
-FAIL: gdb.threads/tls.exp: 5 info address a_thread_local
-FAIL: gdb.threads/tls.exp: 5 info address another_thread_local
-PASS: gdb.threads/tls.exp: selected thread: 3
-PASS: gdb.threads/tls.exp: thread 3 up
-PASS: gdb.threads/tls.exp: 3 thread print me
-FAIL: gdb.threads/tls.exp: 3 thread local storage
-FAIL: gdb.threads/tls.exp: 3 another thread local storage
-FAIL: gdb.threads/tls.exp: 3 info address a_thread_local
-FAIL: gdb.threads/tls.exp: 3 info address another_thread_local
-PASS: gdb.threads/tls.exp: threads exited
-PASS: gdb.threads/tls.exp: Expect only base thread at end
-PASS: gdb.threads/tls.exp: info address a_global
-KFAIL: gdb.threads/tls.exp: info address me (PRMS: gdb/1294)
+FAIL: gdb.threads/tls.exp: continue to third thread (timeout)
+FAIL: gdb.threads/tls.exp: at least one th in spin while stopped at third th (timeout)
+FAIL: gdb.threads/tls.exp: third thread print me (timeout)
+FAIL: gdb.threads/tls.exp: third thread local storage (timeout)
+FAIL: gdb.threads/tls.exp: third another thread local storage (timeout)
+FAIL: gdb.threads/tls.exp: third info address a_thread_local (timeout)
+FAIL: gdb.threads/tls.exp: third info address another_thread_local (timeout)
+FAIL: gdb.threads/tls.exp: continue to synch point (timeout)
+FAIL: gdb.threads/tls.exp: get number of threads (timeout)
+FAIL: gdb.threads/tls.exp: No thread backtrace reported spin (vsyscall kernel problem?)
+FAIL: gdb.threads/tls.exp: threads exited (timeout)
+FAIL: gdb.threads/tls.exp: at end (timeout)
+ERROR: Delete all breakpoints in delete_breakpoints (timeout)
+UNRESOLVED: gdb.threads/tls.exp: setting breakpoint at spin (timeout)
+FAIL: gdb.threads/tls.exp: info address a_global (timeout)
+KFAIL: gdb.threads/tls.exp: info address me (timeout) (PRMS: gdb/1294)
 Running ./gdb.trace/actions.exp ...
 PASS: gdb.trace/actions.exp: 5.1a: set three tracepoints, no actions
 PASS: gdb.trace/actions.exp: 5.1b: set actions for first tracepoint
@@ -10183,12 +9969,13 @@
 
 		=== gdb Summary ===
 
-# of expected passes		9703
-# of unexpected failures	54
+# of expected passes		9442
+# of unexpected failures	96
 # of unexpected successes	1
 # of expected failures		65
-# of known failures		36
+# of known failures		35
+# of unresolved testcases	1
 # of untested testcases		6
-# of unsupported tests		2
-/gdb/mirror/src/gdb/testsuite/../../gdb/gdb version  2003-11-12-cvs -nx
+# of unsupported tests		6
+/gdb/mirror/src/gdb/testsuite/../../gdb/gdb version  2003-11-14-cvs -nx
 

Re: GDB regressions

[David Carlton]

On Fri, 14 Nov 2003 13:37:45 -0800, David Carlton <carlton@kealia.com> said:

> I just did a CVS update, and I got a whole bunch of regressions.  I'll
> include the diff of the gdb.sums after my signatures; these have all
> appeared since Wednesday some time.

Whoops, I forgot some info.  i686-pc-linux-gnu, GCC 3.2, Red Hat 8.0.

David Carlton
carlton@kealia.com

Re: GDB regressions

[Daniel Jacobowitz]

On Fri, Nov 14, 2003 at 01:37:45PM -0800, David Carlton wrote:
> I just did a CVS update, and I got a whole bunch of regressions.  I'll
> include the diff of the gdb.sums after my signatures; these have all
> appeared since Wednesday some time.

+UNSUPPORTED: gdb.threads/gcore-thread.exp: gdb does not support threads on this target

Why's it doing that?  Has anything else on your system changed since
you last ran the testsuite?

It still seems OK here.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: GDB regressions

[David Carlton]

On Fri, 14 Nov 2003 16:57:02 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> On Fri, Nov 14, 2003 at 01:37:45PM -0800, David Carlton wrote:

>> I just did a CVS update, and I got a whole bunch of regressions.
>> I'll include the diff of the gdb.sums after my signatures; these
>> have all appeared since Wednesday some time.

> +UNSUPPORTED: gdb.threads/gcore-thread.exp: gdb does not support threads on this target

> Why's it doing that?  Has anything else on your system changed since
> you last ran the testsuite?

The only thing I can think of is that I installed new versions of the
glibc RPMs (and installed the glibc-debug rpm, which I hadn't had at
all before, but that goes in a directory that isn't in my
LD_LIBRARY_PATH).  So it could be a bug in them, I suppose.

Hopefully I'll be upgrading to Red Hat 9.0 later today; maybe it will
go away with that.

David Carlton
carlton@kealia.com

Re: GDB regressions

[Daniel Jacobowitz]

On Fri, Nov 14, 2003 at 02:11:48PM -0800, David Carlton wrote:
> On Fri, 14 Nov 2003 16:57:02 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> > On Fri, Nov 14, 2003 at 01:37:45PM -0800, David Carlton wrote:
> 
> >> I just did a CVS update, and I got a whole bunch of regressions.
> >> I'll include the diff of the gdb.sums after my signatures; these
> >> have all appeared since Wednesday some time.
> 
> > +UNSUPPORTED: gdb.threads/gcore-thread.exp: gdb does not support threads on this target
> 
> > Why's it doing that?  Has anything else on your system changed since
> > you last ran the testsuite?
> 
> The only thing I can think of is that I installed new versions of the
> glibc RPMs (and installed the glibc-debug rpm, which I hadn't had at
> all before, but that goes in a directory that isn't in my
> LD_LIBRARY_PATH).  So it could be a bug in them, I suppose.

Most likely that's it.  Thread debugging is not working at all if you
see that message.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: GDB regressions

[Mark Kettenis]

   From: David Carlton <carlton@kealia.com>
   Date: Fri, 14 Nov 2003 14:11:48 -0800

   On Fri, 14 Nov 2003 16:57:02 -0500, Daniel Jacobowitz <drow@mvista.com> said:
   > On Fri, Nov 14, 2003 at 01:37:45PM -0800, David Carlton wrote:

   >> I just did a CVS update, and I got a whole bunch of regressions.
   >> I'll include the diff of the gdb.sums after my signatures; these
   >> have all appeared since Wednesday some time.

   > +UNSUPPORTED: gdb.threads/gcore-thread.exp: gdb does not support threads on this target

   > Why's it doing that?  Has anything else on your system changed since
   > you last ran the testsuite?

   The only thing I can think of is that I installed new versions of the
   glibc RPMs (and installed the glibc-debug rpm, which I hadn't had at
   all before, but that goes in a directory that isn't in my
   LD_LIBRARY_PATH).  So it could be a bug in them, I suppose.

It's very well possible I'm to blame for some of the problems you're
seeing (although not the thread-related ones I think).  I just
committed a patch which should fix it if I did indeed break things:

http://sources.redhat.com/ml/gdb-patches/2003-11/msg00319.html

Mark

Re: GDB regressions

[David Carlton]

On Fri, 14 Nov 2003 17:15:41 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> On Fri, Nov 14, 2003 at 02:11:48PM -0800, David Carlton wrote:
>> On Fri, 14 Nov 2003 16:57:02 -0500, Daniel Jacobowitz <drow@mvista.com> said:

>>> Why's it doing that?  Has anything else on your system changed
>>> since you last ran the testsuite?

>> The only thing I can think of is that I installed new versions of
>> the glibc RPMs (and installed the glibc-debug rpm, which I hadn't
>> had at all before, but that goes in a directory that isn't in my
>> LD_LIBRARY_PATH).  So it could be a bug in them, I suppose.

> Most likely that's it.  Thread debugging is not working at all if
> you see that message.

Yeah, that's it.  I can't retry on the computer in question (I'm in
the middle of a botched RH8->9 upgrade on it - why can't RH9 find my
external monitor?), but I just tried on my home machine, where I have
the new glibc but haven't done a CVS update on my GDB directory for a
while, and I'm seeing similar issues there.

Sorry for the false alarm.

David Carlton
carlton@kealia.com

Re: GDB regressions

[Michael Elizabeth Chastain]

David Carlton writes:
> I just did a CVS update, and I got a whole bunch of regressions.  I'll
> include the diff of the gdb.sums after my signatures; these have all
> appeared since Wednesday some time.

Just for a data point, I just finished a test spin and I didn't see
this happening.  I have native i686-pc-linux-gnu, red hat linux 8,
vendor glibc without debugging symbols.

Michael C

Re: GDB regressions

[Michael Elizabeth Chastain]

This is not ringing any bells in my cache.

I'm doing a spin tonight and I'll have my next report in about 15 hours,
plus the time it takes me to write the report (which might be a bit
longer).  Let's see if I see something similar with my red hat linux
8.0.

Meanwhile, do you still have the gdb.log from the bad test run?
Can you mail that to me?

Michael C