This is the mail archive of the gdb-testers@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Failures on Fedora-x86_64-native-gdbserver-m32, branch master


Buildslave:
	fedora-x86-64-2

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-gdbserver-m32/builds/181>

Commit(s) tested:
	f7de9aab902f68a79e83954d2645daf90f9eae33

Author(s) (in the same order as the commits):
	Mark Wielaard <mjw@redhat.com>

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-x86_64-native-gdbserver-m32/.git/tree/?h=master&id=e082caaac48c4b2f3f1bc17b6e1b9db1dddd4263>

*** Regressions found ***
============================
PASS -> FAIL: gdb.threads/next-bp-other-thread.exp: schedlock=step: next over function call
PASS -> FAIL: gdb.threads/watchthreads2.exp: all threads started
new FAIL: gdb.threads/watchthreads2.exp: run to thread_started
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.base/corefile.exp: core-file warning-free
PASS -> FAIL: gdb.base/disp-step-syscall.exp: vfork: delete break vfork insn
PASS -> FAIL: gdb.base/disp-step-syscall.exp: vfork: single step over vfork final pc
PASS -> FAIL: gdb.base/restore.exp: caller3 calls callee1; return restored l1 to 32492
PASS -> FAIL: gdb.base/restore.exp: caller3 calls callee2; return restored l1 to 32492
PASS -> FAIL: gdb.base/restore.exp: caller3 calls callee3; return restored l1 to 32492
PASS -> FAIL: gdb.base/restore.exp: caller3 calls callee4; return restored l1 to 32492
PASS -> FAIL: gdb.base/restore.exp: caller3 calls callee5; return restored l1 to 32492
PASS -> FAIL: gdb.base/restore.exp: caller4 calls callee1; return restored l1 to 32492
PASS -> FAIL: gdb.base/restore.exp: caller4 calls callee1; return restored l2 to 32493
PASS -> FAIL: gdb.base/restore.exp: caller4 calls callee2; return restored l1 to 32492
PASS -> FAIL: gdb.base/restore.exp: caller4 calls callee2; return restored l2 to 32493
PASS -> FAIL: gdb.base/restore.exp: caller4 calls callee3; return restored l1 to 32492
PASS -> FAIL: gdb.base/restore.exp: caller4 calls callee3; return restored l2 to 32493
PASS -> FAIL: gdb.base/restore.exp: caller4 calls callee4; return restored l1 to 32492
PASS -> FAIL: gdb.base/restore.exp: caller4 calls callee4; return restored l2 to 32493
PASS -> FAIL: gdb.base/restore.exp: caller4 calls callee5; return restored l1 to 32492
PASS -> FAIL: gdb.base/restore.exp: caller4 calls callee5; return restored l2 to 32493
PASS -> FAIL: gdb.base/restore.exp: caller5 calls callee1; return restored l2 to 32493
PASS -> FAIL: gdb.base/restore.exp: caller5 calls callee1; return restored l3 to 32494
PASS -> FAIL: gdb.base/restore.exp: caller5 calls callee2; return restored l2 to 32493
PASS -> FAIL: gdb.base/restore.exp: caller5 calls callee2; return restored l3 to 32494
PASS -> FAIL: gdb.base/restore.exp: caller5 calls callee3; return restored l2 to 32493
PASS -> FAIL: gdb.base/restore.exp: caller5 calls callee3; return restored l3 to 32494
PASS -> FAIL: gdb.base/restore.exp: caller5 calls callee4; return restored l2 to 32493
PASS -> FAIL: gdb.base/restore.exp: caller5 calls callee4; return restored l3 to 32494
PASS -> FAIL: gdb.base/restore.exp: caller5 calls callee5; return restored l2 to 32493
PASS -> FAIL: gdb.base/restore.exp: caller5 calls callee5; return restored l3 to 32494
PASS -> FAIL: gdb.base/store.exp: upvar longest l; print old r, expecting -2
PASS -> FAIL: gdb.base/store.exp: var longest l; print old r, expecting -2
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: check FinishBreakpoint in catch()
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: check finish BP removal
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: continue to second exception
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception <<2>>
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: all dummies popped
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: dummy stack frame number, thread 2
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: dummy stack frame number, thread 3
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: dummy stack frame number, thread 4
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: hand call, thread 2
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: hand call, thread 3
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: hand call, thread 4
PASS -> FAIL: gdb.threads/next-bp-other-thread.exp: schedlock=step: next over function call
PASS -> FAIL: gdb.threads/no-unwaited-for-left.exp: continue stops when the main thread exits
PASS -> FAIL: gdb.threads/no-unwaited-for-left.exp: continue stops when thread 2 exits
PASS -> FAIL: gdb.threads/watchthreads2.exp: all threads started
new FAIL: gdb.threads/watchthreads2.exp: run to thread_started
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 1 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 10 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 11 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 12 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 13 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 14 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 15 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 16 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 17 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 18 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 19 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 2 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 20 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 21 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 22 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 23 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 24 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 25 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 26 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 27 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 28 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 29 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 3 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 30 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 31 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 32 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 33 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 34 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 35 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 36 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 37 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 38 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 39 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 4 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 40 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 41 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 42 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 43 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 44 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 45 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 46 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 47 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 48 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 49 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 5 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 50 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 51 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 52 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 53 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 54 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 55 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 56 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 57 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 58 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 59 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 6 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 60 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 61 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 62 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 63 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 64 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 65 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 66 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 67 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 68 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 69 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 7 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 70 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 71 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 72 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 73 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 74 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 75 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 76 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 77 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 78 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 79 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 8 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 80 out of 80 on watched_data (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Continue to watchpoint trigger 9 out of 80 on watched_data (the program is no longer running)
PASS -> FAIL: gdb.threads/wp-replication.exp: Thread 6 hit breakpoint at thread_started
PASS -> FAIL: gdb.threads/wp-replication.exp: Thread 7 hit breakpoint at thread_started
new FAIL: gdb.threads/wp-replication.exp: Thread 8 hit breakpoint at thread_started (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Thread 9 hit breakpoint at thread_started (the program is no longer running)
PASS -> FAIL: gdb.threads/wp-replication.exp: set var test_ready=1
============================


*** Failures that are being ignored ***
============================
FAIL: gdb.ada/interface.exp: print s
FAIL: gdb.ada/iwide.exp: print My_Drawable
FAIL: gdb.ada/iwide.exp: print d_access.all
FAIL: gdb.ada/iwide.exp: print dp_access.all
FAIL: gdb.ada/iwide.exp: print s_access.all
FAIL: gdb.ada/iwide.exp: print sp_access.all
FAIL: gdb.ada/mi_interface.exp: Create ggg1 varobj
FAIL: gdb.ada/mi_interface.exp: list ggg1's children
FAIL: gdb.ada/ptype_tagged_param.exp: ptype s
FAIL: gdb.ada/str_uninit.exp: print my_str
FAIL: gdb.ada/tagged.exp: print obj
FAIL: gdb.ada/tagged.exp: ptype obj
FAIL: gdb.ada/tagged_access.exp: ptype c.all
FAIL: gdb.ada/tagged_access.exp: ptype c.menu_name
FAIL: gdb.threads/next-bp-other-thread.exp: schedlock=off: next over function call
FAIL: gdb.base/random-signal.exp: stop with control-c (timeout)
FAIL: gdb.threads/local-watch-wrong-thread.exp: breakpoint on thread_function0's caller (timeout)
FAIL: gdb.threads/local-watch-wrong-thread.exp: delete 5 (timeout)
FAIL: gdb.threads/local-watch-wrong-thread.exp: let local watchpoint trigger (timeout)
FAIL: gdb.threads/local-watch-wrong-thread.exp: let thread_function0 return (timeout)
FAIL: gdb.threads/local-watch-wrong-thread.exp: local watchpoint automatically deleted (timeout)
FAIL: gdb.threads/local-watch-wrong-thread.exp: local watchpoint is still in breakpoint list (timeout)
FAIL: gdb.threads/local-watch-wrong-thread.exp: local watchpoint still triggers (timeout)
FAIL: gdb.threads/local-watch-wrong-thread.exp: the other thread stopped on breakpoint (timeout)
FAIL: gdb.threads/hand-call-in-threads.exp: dummy stack frame number, thread 5
FAIL: gdb.threads/hand-call-in-threads.exp: hand call, thread 5
FAIL: gdb.threads/wp-replication.exp: Thread 5 hit breakpoint at thread_started
============================




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]