gdb test results, gcc-3.3 on hppa-linux

[Randolph Chung <randolph at tausq dot org>]

gcc version 3.3.3 (Debian 20040306)
binutils 2.14.90.0.7
glibc 2.3.2
Linux legolas 2.6.7-rc1-pa1 #31 Mon May 24 08:51:58 PDT 2004 parisc GNU/Linux

gdb HEAD from 20040606, with the following patches:
http://sources.redhat.com/ml/gdb-patches/2004-05/msg00657.html
http://sources.redhat.com/ml/gdb/2004-05/msg00161.html
http://sources.redhat.com/ml/gdb-patches/2004-06/msg00108.html
http://sources.redhat.com/ml/gdb-patches/2004-06/msg00109.html

                === gdb Summary ===

# of expected passes            10139
# of unexpected failures        57
# of unexpected successes       2
# of expected failures          46
# of known failures             36
# of unresolved testcases       4
# of untested testcases         9
# of unsupported tests          3

FAIL: gdb.ada/null_record.exp: ptype on null record
FAIL: gdb.base/annota1.exp: send SIGUSR1
FAIL: gdb.base/annota3.exp: send SIGUSR1 (pattern 6)
FAIL: gdb.base/annota3.exp: backtrace @ signal handler (pattern 1)
FAIL: gdb.base/call-ar-st.exp: print print_long_arg_list (pattern 1)
FAIL: gdb.base/callfuncs.exp: bt after continuing from call dummy breakpoint
FAIL: gdb.base/commands.exp: continue with watch
FAIL: gdb.base/float.exp: info float
FAIL: gdb.base/help.exp: help breakpoints
FAIL: gdb.base/interrupt.exp: call function when asleep (stays asleep)
FAIL: gdb.base/interrupt.exp: call function after waking it
FAIL: gdb.base/signals.exp: continue to handler
FAIL: gdb.base/signals.exp: continue in signals.exp
FAIL: gdb.base/signals.exp: p count #2 in signals.exp
FAIL: gdb.base/store.exp: print add  - charest
FAIL: gdb.base/store.exp: print add  - short
FAIL: gdb.base/structs2.exp: structs2 continue1 (PRMS 13536)
FAIL: gdb.base/structs2.exp: structs2 continue2 (PRMS 13536)
FAIL: gdb.base/watchpoint.exp: continue to read
FAIL: gdb.base/watchpoint.exp: watch tests suppressed
FAIL: gdb.base/watchpoint.exp: (timeout) disable fast watches
FAIL: gdb.base/watchpoint.exp: (timeout) show disable fast watches
FAIL: gdb.base/watchpoint.exp: (timeout) set slow conditional watch
FAIL: gdb.base/watchpoint.exp: (timeout) trigger slow conditional watch
FAIL: gdb.base/watchpoint.exp: (timeout) rwatch disallowed when can-use-hw-watchpoints cleared
FAIL: gdb.cp/annota3.exp: annotate-quit (pattern 1)
FAIL: gdb.cp/bs15503.exp: print (const char *) s.substr(0,4)
FAIL: gdb.cp/bs15503.exp: print (const char *) (s=s.substr(0,4))
FAIL: gdb.cp/templates.exp: ptype Baz
FAIL: gdb.mi/mi-basics.exp: environment-directory arg operation
FAIL: gdb.mi/mi-basics.exp: environment-directory empty-string operation
FAIL: gdb.mi/mi-basics.exp: environment-path dir1 dir2 operation
FAIL: gdb.mi/mi-cli.exp: -interpreter-exec console "set $pc=0x0"
FAIL: gdb.mi/mi-syn-frame.exp: 403-exec-continue
FAIL: gdb.mi/mi-syn-frame.exp: 404-stack-list-frames 0 0
FAIL: gdb.mi/mi-syn-frame.exp: 405-break-insert subroutine
FAIL: gdb.mi/mi-syn-frame.exp: 406-data-evaluate-expression have_a_very_merry_interrupt()
FAIL: gdb.mi/mi-syn-frame.exp: 407-stack-list-frames
FAIL: gdb.mi/mi-syn-frame.exp: 408-exec-continue
FAIL: gdb.mi/mi-syn-frame.exp: 409-stack-list-frames 0 0
FAIL: gdb.mi/mi-watch.exp: wp out of scope (2)
FAIL: gdb.mi/mi2-basics.exp: environment-directory arg operation
FAIL: gdb.mi/mi2-basics.exp: environment-directory empty-string operation
FAIL: gdb.mi/mi2-basics.exp: environment-path dir1 dir2 operation
FAIL: gdb.mi/mi2-cli.exp: -interpreter-exec console "set $pc=0x0"
FAIL: gdb.mi/mi2-syn-frame.exp: 403-exec-continue
FAIL: gdb.mi/mi2-syn-frame.exp: 404-stack-list-frames 0 0
FAIL: gdb.mi/mi2-syn-frame.exp: 408-exec-continue
FAIL: gdb.mi/mi2-syn-frame.exp: 409-stack-list-frames 0 0
FAIL: gdb.mi/mi2-syn-frame.exp: call inferior function which raises exception
FAIL: gdb.mi/mi2-watch.exp: wp out of scope (2)
FAIL: gdb.objc/basicclass.exp: Call an Objective-C method with no arguments
FAIL: gdb.objc/basicclass.exp: Call an Objective-C method with one argument
FAIL: gdb.threads/print-threads.exp: Running threads (slow with kill breakpoint) (timeout)
FAIL: gdb.threads/pthreads.exp: apply backtrace command to all three threads
FAIL: gdb.threads/schedlock.exp: thread 0 ran (didn't run)
FAIL: gdb.threads/schedlock.exp: thread 1 ran (didn't run)

-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/