This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
Failures on Fedora-x86_64-m64, branch gdb-8.1-branch
- From: sergiodj+buildbot at sergiodj dot net
- To: gdb-testers at sourceware dot org
- Date: Thu, 10 May 2018 12:31:10 -0400
- Subject: Failures on Fedora-x86_64-m64, branch gdb-8.1-branch
Buildslave:
fedora-x86-64-3
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m64/builds/9673>
Commit(s) tested:
8a620990c7634e872b31718a8411a90a6f384457
Author(s) (in the same order as the commits):
Omair Javaid <omair.javaid@linaro.org>
Subject:
Fix tagged pointer support
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-x86_64-m64/8a/8a620990c7634e872b31718a8411a90a6f384457/>
*** Diff to previous build ***
============================
PASS -> FAIL: gdb.arch/amd64-i386-address.exp: trap stop
PASS -> FAIL: gdb.arch/amd64-i386-address.exp: x/wx $esp
PASS -> FAIL: gdb.arch/amd64-i386-address.exp: x/wx $ebx
PASS -> FAIL: gdb.base/info-os.exp: continue to breakpoint: Set breakpoint here
PASS -> FAIL: gdb.base/info-os.exp: get shared memory key
PASS -> FAIL: gdb.base/info-os.exp: get shared memory ID
PASS -> FAIL: gdb.base/info-os.exp: get semaphore key
PASS -> FAIL: gdb.base/info-os.exp: get semaphore ID
PASS -> FAIL: gdb.base/info-os.exp: get message queue key
PASS -> FAIL: gdb.base/info-os.exp: get message queue ID
PASS -> FAIL: gdb.base/info-os.exp: get socket port number
PASS -> FAIL: gdb.base/info-os.exp: get process list
new KFAIL: gdb.base/step-over-syscall.exp: clone: displaced=on: single step over clone
PASS -> FAIL: gdb.multi/multi-arch-exec.exp: first_arch=1: selected_thread=1: follow_exec_mode=same: continue across exec that changes architecture
PASS -> FAIL: gdb.multi/multi-arch-exec.exp: first_arch=1: selected_thread=1: follow_exec_mode=new: continue across exec that changes architecture
PASS -> FAIL: gdb.multi/multi-arch-exec.exp: first_arch=1: selected_thread=2: follow_exec_mode=same: continue across exec that changes architecture
PASS -> FAIL: gdb.multi/multi-arch-exec.exp: first_arch=1: selected_thread=2: follow_exec_mode=new: continue across exec that changes architecture
new FAIL: gdb.multi/multi-arch-exec.exp: first_arch=2: selected_thread=1: follow_exec_mode=same: couldn't run to all_started
new FAIL: gdb.multi/multi-arch-exec.exp: first_arch=2: selected_thread=1: follow_exec_mode=new: couldn't run to all_started
new FAIL: gdb.multi/multi-arch-exec.exp: first_arch=2: selected_thread=2: follow_exec_mode=same: couldn't run to all_started
new FAIL: gdb.multi/multi-arch-exec.exp: first_arch=2: selected_thread=2: follow_exec_mode=new: couldn't run to all_started
new FAIL: gdb.multi/multi-arch.exp: starting inferior 2
PASS -> FAIL: gdb.multi/multi-arch.exp: info inferiors
PASS -> FAIL: gdb.multi/multi-arch.exp: set schedule-multiple on
PASS -> FAIL: gdb.multi/multi-arch.exp: inf1 event with inf2 selected: inferior 2
PASS -> FAIL: gdb.multi/multi-arch.exp: inf1 event with inf2 selected: b hello_loop
PASS -> FAIL: gdb.multi/multi-arch.exp: inf1 event with inf2 selected: continue to hello_loop
new FAIL: gdb.multi/multi-arch.exp: delete all breakpoints in delete_breakpoints
PASS -> FAIL: gdb.multi/multi-arch.exp: inf2 event with inf1 selected: b hangout_loop
PASS -> FAIL: gdb.multi/multi-arch.exp: inf2 event with inf1 selected: continue to hangout_loop
PASS -> KFAIL: gdb.threads/non-ldr-exit.exp: program exits normally
PASS -> FAIL: gdb.threads/watchpoint-fork.exp: child: multithreaded: breakpoint
============================
*** Complete list of XFAILs for this builder ***
FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST. PLEASE CONTACT THE BUILDBOT ADMIN.