This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-8.1-branch
- From: sergiodj+buildbot at sergiodj dot net
- To: gdb-testers at sourceware dot org
- Date: Wed, 28 Feb 2018 22:26:27 -0500
- Subject: Failures on Fedora-x86_64-native-gdbserver-m32, branch gdb-8.1-branch
- Authentication-results: sourceware.org; auth=none
Buildslave:
fedora-x86-64-4
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-gdbserver-m32/builds/8924>
Commit(s) tested:
2441702a72f324e41a1624dc042b334f375e2d81
Author(s) (in the same order as the commits):
Sergio Durigan Junior <sergiodj@redhat.com>
Subject:
Make gdbserver work with filename-only binaries
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-x86_64-native-gdbserver-m32/24/2441702a72f324e41a1624dc042b334f375e2d81/>
*** Diff to previous build ***
============================
new FAIL: gdb.base/interrupt.exp: echo data
new FAIL: gdb.base/interrupt.exp: Send Control-C, second time
new FAIL: gdb.base/interrupt.exp: signal SIGINT
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: continue to breakpoint: run to breakpoint in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: next: setup: unbreak loop in thread 3
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: continue to breakpoint: run to breakpoint in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: setup: unbreak loop in thread 2
PASS -> FAIL: gdb.threads/multiple-step-overs.exp: displaced=on: signal thr3: continue to sigusr1_handler
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited
new KFAIL: gdb.threads/watchthreads2.exp: gdb can drop watchpoints in multithreaded app
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.