This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master
- From: sergiodj+buildbot at redhat dot com
- To: gdb-testers at sourceware dot org
- Date: Fri, 15 May 2015 16:23:30 -0400
- Subject: Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master
- Authentication-results: sourceware.org; auth=none
Buildslave:
wildebeest-debian-wheezy-x86_64
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Debian-x86_64-native-extended-gdbserver-m64/builds/1023>
Commit(s) tested:
4e63d0ac896b6036edd8e2c09a4dac7aa16a46d1
Author(s) (in the same order as the commits):
Pedro Alves <palves@redhat.com>
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/cgit/Debian-x86_64-native-extended-gdbserver-m64/.git/tree/?h=master&id=aac3cafb6838e24126d6bfcc836ed5f5e16993b4>
*** Regressions found ***
============================
new FAIL: gdb.base/checkpoint.exp: break3 one (the program exited)
new FAIL: gdb.base/checkpoint.exp: step in 1 one
new FAIL: gdb.base/checkpoint.exp: step in 10 one
new FAIL: gdb.base/checkpoint.exp: step in 2 one
new FAIL: gdb.base/checkpoint.exp: step in 3 one
new FAIL: gdb.base/checkpoint.exp: step in 4 one
new FAIL: gdb.base/checkpoint.exp: step in 5 one
new FAIL: gdb.base/checkpoint.exp: step in 6 one
new FAIL: gdb.base/checkpoint.exp: step in 7 one
new FAIL: gdb.base/checkpoint.exp: step in 8 one
new FAIL: gdb.base/checkpoint.exp: step in 9 one
PASS -> FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit
============================
*** Regressions against the baseline ***
============================
new FAIL: gdb.base/attach.exp: cmdline attach run: run to main
new FAIL: gdb.base/foll-vfork.exp: exec: vfork and exec child follow, to main bp: continue to bp
new FAIL: gdb.base/foll-vfork.exp: exec: vfork child follow, finish after tcatch vfork: finish
new FAIL: gdb.base/foll-vfork.exp: exec: vfork parent follow, to bp: continue to bp
new FAIL: gdb.base/foll-vfork.exp: exec: vfork relations in info inferiors: continue to bp
PASS -> FAIL: gdb.base/foll-vfork.exp: exec: vfork relations in info inferiors: vfork relation no longer appears in info inferiors
new FAIL: gdb.base/foll-vfork.exp: exit: vfork parent follow, to bp: continue to bp
new FAIL: gdb.gdb/python-selftest.exp: call catch_command_errors(execute_command, "python print(5)", 0)
PASS -> FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit
============================
*** Failures that are being ignored ***
============================
FAIL: gdb.base/random-signal.exp: stop with control-c (timeout)
FAIL: gdb.dwarf2/gdb-index.exp: touch binary
FAIL: gdb.threads/next-bp-other-thread.exp: schedlock=off: next over function call============================