public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj@redhat.com
To: gdb-testers@sourceware.org
Subject: Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.9-branch
Date: Thu, 19 Feb 2015 17:07:00 -0000 [thread overview]
Message-ID: <E1YOTup-0003IK-SB@kwanyin.sergiodj.net> (raw)
In-Reply-To: <3b41352824ddc32dabca2d3281a03b4a0b8c7a27@kwanyin>
Buildslave:
fedora-x86-64-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-gdbserver-m32/builds/265>
Commit(s) tested:
3b41352824ddc32dabca2d3281a03b4a0b8c7a27
Author(s) (in the same order as the commits):
Joel Brobecker <brobecker@adacore.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=gdb-7.9-branch&id=8d7219bc6a24ee0e39e7be62d9346bb07febc074>
*** Regressions found ***
============================
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 2 hit breakpoint at thread_started
PASS -> FAIL: gdb.threads/wp-replication.exp: Thread 3 hit breakpoint at thread_started
new FAIL: gdb.threads/wp-replication.exp: Thread 4 hit breakpoint at thread_started (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Thread 5 hit breakpoint at thread_started (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Thread 6 hit breakpoint at thread_started (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Thread 7 hit breakpoint at thread_started (the program is no longer running)
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
============================
*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: dummy stack frame number, thread 5
PASS -> FAIL: gdb.threads/hand-call-in-threads.exp: hand call, thread 5
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 2 hit breakpoint at thread_started
PASS -> FAIL: gdb.threads/wp-replication.exp: Thread 3 hit breakpoint at thread_started
new FAIL: gdb.threads/wp-replication.exp: Thread 4 hit breakpoint at thread_started (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Thread 5 hit breakpoint at thread_started (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Thread 6 hit breakpoint at thread_started (the program is no longer running)
new FAIL: gdb.threads/wp-replication.exp: Thread 7 hit breakpoint at thread_started (the program is no longer running)
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.base/disp-step-syscall.exp: vfork: continue to marker (vfork)
============================
next prev parent reply other threads:[~2015-02-19 16:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 15:26 Test results for commit 3b41352824ddc32dabca2d3281a03b4a0b8c7a27 on " sergiodj
2015-02-19 15:30 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj
2015-02-19 16:09 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-19 16:17 ` Failures on Fedora-ppc64be-m64, " sergiodj
2015-02-19 16:23 ` Failures on Fedora-x86_64-m32, " sergiodj
2015-02-19 16:32 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj
2015-02-19 16:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj
2015-02-19 17:07 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj
2015-02-19 17:07 ` sergiodj [this message]
2015-02-19 17:09 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj
2015-02-19 17:16 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj
2015-02-19 17:29 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj
2015-02-19 18:05 ` Failures on Fedora-ppc64le-m64, " sergiodj
2015-02-19 20:39 ` Failures on Debian-i686, " sergiodj
2015-02-19 21:29 ` Failures on Debian-i686-native-gdbserver, " sergiodj
2015-02-20 0:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj
2015-02-20 0:44 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj
-- strict thread matches above, loose matches on Subject: below --
2015-05-30 11:03 [binutils-gdb/gdb-7.9-branch] Unbreak DJGPP build of GDB sergiodj+buildbot
2015-05-30 14:41 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.9-branch sergiodj+buildbot
2015-05-13 17:56 [binutils-gdb/gdb-7.9-branch] Bump GDB version number to 7.9.1.DATE-cvs sergiodj+buildbot
2015-05-14 2:38 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.9-branch sergiodj+buildbot
2015-05-12 16:20 [binutils-gdb/gdb-7.9-branch] PR python/18285 sergiodj+buildbot
2015-05-12 18:18 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.9-branch sergiodj+buildbot
2015-04-29 6:16 [binutils-gdb/gdb-7.9-branch] PR python/18299 sergiodj+buildbot
2015-04-29 11:22 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.9-branch sergiodj+buildbot
2015-03-31 15:30 [binutils-gdb/gdb-7.9-branch] Fix the triplet regexp to recognize triplets, not only quadruplets sergiodj+buildbot
2015-04-03 12:14 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.9-branch sergiodj+buildbot
2015-02-26 12:11 [binutils-gdb/gdb-7.9-branch] Remove // comment in gdb/iq2000-tdep.c sergiodj+buildbot
2015-02-26 13:24 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-7.9-branch sergiodj+buildbot
2015-02-20 18:08 Test results for commit 1435f081d10098b0bff7e30273c1c2611c35c4f9 on " sergiodj
2015-02-20 19:21 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj
2015-02-20 5:01 Test results for commit 7b582627bc42922de3b75792472f5223f1910277 on " sergiodj
2015-02-20 9:50 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj
2015-02-20 4:06 Test results for commit 3b7a39661610038aad32563069b10fb2cfc55fab on " sergiodj
2015-02-20 9:00 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj
2015-02-19 13:35 Test results for commit 90ca3b45da1c08eff31605b2af7cec9979a95bde on " sergiodj
2015-02-19 14:45 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj
2015-02-17 15:08 Test results for commit 5991bec1d4dbd23b476dc90bc6d1ba70e044898e on " sergiodj
2015-02-17 15:44 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj
2015-02-17 13:49 Test results for commit d4a0a1ff2b7f3d50180229768a270750ef94bbdf on " sergiodj
2015-02-17 14:57 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj
2015-02-17 12:43 Test results for commit 140e2c62fd7a46b4500dbd442964543587c0337b on " sergiodj
2015-02-17 14:21 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj
2015-02-11 17:07 Test results for commit 211e7f3c26b39159df2dedd8198148cec60307f9 on " sergiodj
2015-02-12 23:21 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj
2015-02-11 16:34 Test results for commit cf3f71d273c607ecd1e912ce9fe8121da320c6a9 on " sergiodj
2015-02-12 18:50 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj
2015-02-11 15:19 Test results for commit 46d020960241fcafd7d0ab483746a206829620ea on " sergiodj
2015-02-12 11:04 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj
2015-02-04 9:21 sergiodj
2015-02-01 13:47 sergiodj
2015-01-30 2:33 sergiodj
2015-01-29 20:32 sergiodj
2015-01-29 3:10 sergiodj
2015-01-28 2:51 sergiodj
2015-01-27 2:33 sergiodj
2015-01-26 18:50 sergiodj
2015-01-26 0:45 sergiodj
2015-01-25 12:57 sergiodj
2015-01-25 4:24 sergiodj
2015-01-24 3:34 sergiodj
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=E1YOTup-0003IK-SB@kwanyin.sergiodj.net \
--to=sergiodj@redhat.com \
--cc=gdb-testers@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).