Failures on Fedora-x86_64-m64, branch gdb-7.10-branch
sergiodj+buildbot@redhat.com
sergiodj+buildbot@redhat.com
Tue Dec 1 10:26:00 GMT 2015
Buildslave:
fedora-x86-64-2
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m64/builds/2526>
Commit(s) tested:
9a2752c7f09d24865b33fedd9ac2585f3cbba3c3
Author(s) (in the same order as the commits):
Pedro Alves <palves@redhat.com>
Subject:
Adjust GDB to demangler API change
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=18ecb6e3403cc15ebc7b00aeb83a1f325a15c05a>
*** Regressions found ***
============================
new FAIL: gdb.base/annota3.exp: signal sent (pattern 4) (timeout)
============================
*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.ada/info_exc.exp: info exceptions
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
new FAIL: gdb.base/annota3.exp: signal sent (pattern 4) (timeout)
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: without semaphore, optimized: set multi-location probe breakpoint (probe two)
PASS -> FAIL: gdb.base/stap-probe.exp: with 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 ee
PASS -> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype EE
PASS -> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype E2
PASS -> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype E
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/var-tag.exp: in main: c++: ptype E2
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 ee
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 E2
PASS -> FAIL: gdb.cp/virtbase.exp: print *this
PASS -> FAIL: gdb.cp/virtbase.exp: print *(D *) e
new FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled (the program exited)
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.cp/vla-cxx.exp: print c
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: continue to bar (1)
PASS -> FAIL: gdb.opt/inline-bt.exp: backtrace from bar (1)
PASS -> FAIL: gdb.opt/inline-bt.exp: continue to bar (2)
PASS -> FAIL: gdb.opt/inline-bt.exp: backtrace from bar (2)
PASS -> FAIL: gdb.opt/inline-bt.exp: continue to bar (3)
PASS -> FAIL: gdb.opt/inline-bt.exp: backtrace from bar (3)
PASS -> FAIL: gdb.opt/inline-cmds.exp: continue to bar (1)
PASS -> FAIL: gdb.opt/inline-cmds.exp: backtrace from bar (1)
PASS -> FAIL: gdb.opt/inline-cmds.exp: continue to bar (2)
PASS -> FAIL: gdb.opt/inline-cmds.exp: backtrace from bar (2)
PASS -> FAIL: gdb.opt/inline-cmds.exp: continue to marker
PASS -> FAIL: gdb.opt/inline-cmds.exp: backtrace from marker
PASS -> FAIL: gdb.opt/inline-cmds.exp: step into finish marker
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: backtrace from bar (2)
PASS -> FAIL: gdb.opt/inline-locals.exp: continue to bar (3)
PASS -> FAIL: gdb.opt/inline-locals.exp: backtrace from bar (3)
============================
More information about the Gdb-testers
mailing list