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-7.10-branch
- From: sergiodj+buildbot at redhat dot com
- To: gdb-testers at sourceware dot org
- Date: Thu, 06 Aug 2015 13:06:36 -0400
- Subject: Failures on Fedora-x86_64-m64, branch gdb-7.10-branch
- Authentication-results: sourceware.org; auth=none
Buildslave:
fedora-x86-64-1
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m64/builds/1647>
Commit(s) tested:
a01c46276aa3a16c2ac1dae249df14e39d1c281f
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/Fedora-x86_64-m64/.git/tree/?h=gdb-7.10-branch&id=9ce81cd9e22fddd62ac7612b589b3e57c9448b6b>
*** Regressions found ***
============================
PASS -> FAIL: gdb.threads/manythreads.exp: stop threads 2
============================
*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.ada/info_exc.exp: info exceptions
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
PASS -> FAIL: gdb.base/corefile.exp: core-file warning-free
new FAIL: gdb.base/gnu_vector.exp: call add_singlevecs
new FAIL: gdb.base/gnu_vector.exp: continue to add_some_intvecs
new FAIL: gdb.base/gnu_vector.exp: continue to add_some_intvecs (the program is no longer running)
new FAIL: gdb.base/gnu_vector.exp: set vector return value
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint (probe two)
new FAIL: gdb.cp/inherit.exp: print g_vD
new FAIL: gdb.cp/inherit.exp: print g_vE
PASS -> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype E
PASS -> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype E2
PASS -> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype EE
PASS -> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype ee
PASS -> FAIL: gdb.cp/var-tag.exp: in C::f: c++: ptype E
PASS -> FAIL: gdb.cp/var-tag.exp: in C::f: c++: ptype E2
PASS -> FAIL: gdb.cp/var-tag.exp: in C::f: c++: ptype EE
PASS -> FAIL: gdb.cp/var-tag.exp: in C::f: c++: ptype ee
PASS -> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype E
PASS -> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype E2
PASS -> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype EE
PASS -> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype ee
PASS -> FAIL: gdb.cp/virtbase.exp: print *(D *) e
PASS -> FAIL: gdb.cp/virtbase.exp: print *this
new FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
PASS -> FAIL: gdb.cp/vla-cxx.exp: print c
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vla
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref
PASS -> FAIL: gdb.cp/vla-cxx.exp: print vlaref2
PASS -> FAIL: gdb.fortran/library-module.exp: print var_i in lib
PASS -> FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.opt/inline-bt.exp: backtrace from bar (1)
PASS -> FAIL: gdb.opt/inline-bt.exp: backtrace from bar (2)
PASS -> FAIL: gdb.opt/inline-bt.exp: backtrace from bar (3)
PASS -> FAIL: gdb.opt/inline-bt.exp: continue to bar (1)
PASS -> FAIL: gdb.opt/inline-bt.exp: continue to bar (2)
PASS -> FAIL: gdb.opt/inline-bt.exp: continue to bar (3)
PASS -> FAIL: gdb.opt/inline-cmds.exp: backtrace from bar (1)
PASS -> FAIL: gdb.opt/inline-cmds.exp: backtrace from bar (2)
PASS -> FAIL: gdb.opt/inline-cmds.exp: backtrace from marker
PASS -> FAIL: gdb.opt/inline-cmds.exp: continue to bar (1)
PASS -> FAIL: gdb.opt/inline-cmds.exp: continue to bar (2)
PASS -> FAIL: gdb.opt/inline-cmds.exp: continue to marker
PASS -> FAIL: gdb.opt/inline-cmds.exp: step into finish marker
PASS -> FAIL: gdb.opt/inline-locals.exp: backtrace from bar (2)
PASS -> FAIL: gdb.opt/inline-locals.exp: backtrace from bar (3)
PASS -> FAIL: gdb.opt/inline-locals.exp: continue to bar (1)
PASS -> FAIL: gdb.opt/inline-locals.exp: continue to bar (2)
PASS -> FAIL: gdb.opt/inline-locals.exp: continue to bar (3)
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-next over solib function one
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-step back to main one
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-step back to main two
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-step into solib function one
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-step into solib function two
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-step within solib function one
PASS -> FAIL: gdb.reverse/solib-precsave.exp: reverse-step within solib function two
PASS -> FAIL: gdb.reverse/solib-precsave.exp: run until end part two
PASS -> FAIL: gdb.threads/manythreads.exp: stop threads 2
============================