This is the mail archive of the gdb-testers@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Failures on Fedora-i686, branch gdb-7.11-branch


Buildslave:
	fedora-x86-64-1

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Fedora-i686/builds/3605>

Commit(s) tested:
	f0a8d0dc70eddbf1e323e8c07f5092ff5e327548

Author(s) (in the same order as the commits):
	Simon Marchi <simon.marchi@ericsson.com>

Subject:
	Fix double prompt output after run control MI commands with mi-async on (PR 20045)

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Fedora-i686/.git/tree/?h=gdb-7.11-branch&id=8208220fd5d63238b97da240e16feda23c752ce5>

*** Regressions found ***
============================
PASS -> FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end
============================


*** Regressions against the baseline ***
============================
PASS -> FAIL: gdb.arch/i386-signal.exp: backtrace 10
new FAIL: gdb.base/catch-syscall.exp: multiple targets: insert catch syscall on syscall 1 -- write on i386:x86-64
PASS -> FAIL: gdb.base/corefile.exp: core-file warning-free
PASS -> FAIL: gdb.base/stap-probe.exp: without semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/stap-probe.exp: with semaphore, optimized: set multi-location probe breakpoint
PASS -> FAIL: gdb.base/store.exp: var charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.base/store.exp: upvar charest l; print old r, expecting -2 .*
PASS -> FAIL: gdb.cp/vla-cxx.exp: continue to breakpoint: vlas_filled
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
new FAIL: gdb.fortran/library-module.exp: print var_i in lib
new FAIL: gdb.fortran/library-module.exp: print var_i in main
PASS -> FAIL: gdb.python/py-finish-breakpoint2.exp: set FinishBP after the exception
new FAIL: gdb.python/py-finish-breakpoint2.exp: check FinishBreakpoint in catch
new FAIL: gdb.python/py-finish-breakpoint2.exp: check finish BP removal
new FAIL: gdb.python/py-finish-breakpoint2.exp: continue to second exception
PASS -> FAIL: gdb.threads/thread-specific-bp.exp: non-stop: continue to end
============================




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]