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 Debian-x86_64-native-extended-gdbserver-m64, branch master


Buildslave:
	wildebeest-debian-wheezy-x86_64

Full Build URL:
	<http://gdb-build.sergiodj.net/builders/Debian-x86_64-native-extended-gdbserver-m64/builds/1057>

Commit(s) tested:
	c16a3f522a71a20ff6e26599d684a61ac6acecca

Author(s) (in the same order as the commits):
	Omair Javaid <omair.javaid@linaro.org>

Testsuite log (gdb.sum and gdb.log) URL(s):
	<http://gdb-build.sergiodj.net/cgit/Debian-x86_64-native-extended-gdbserver-m64/.git/tree/?h=master&id=e7521352ea687fb4a4f397288110867ace36deb8>

*** Regressions found ***
============================
new FAIL: gdb.threads/fork-thread-pending.exp: 2, followed to the child, found two threads (GDB internal error)
PASS -> FAIL: gdb.threads/fork-thread-pending.exp: 2, get to the fork event
new FAIL: gdb.threads/fork-thread-pending.exp: 2, get to the spawned thread in fork child (the program is no longer running)
new FAIL: gdb.threads/fork-thread-pending.exp: 2, multiple threads found (GDB internal error)
PASS -> FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit
============================


*** Regressions against the baseline ***
============================
new FAIL: gdb.base/attach.exp: cmdline attach run: run to main
new FAIL: gdb.base/foll-vfork.exp: exec: vfork and exec child follow, to main bp: continue to bp
new FAIL: gdb.base/foll-vfork.exp: exec: vfork child follow, finish after tcatch vfork: finish
new FAIL: gdb.base/foll-vfork.exp: exec: vfork parent follow, to bp: continue to bp
new FAIL: gdb.base/foll-vfork.exp: exec: vfork relations in info inferiors: continue to bp
PASS -> FAIL: gdb.base/foll-vfork.exp: exec: vfork relations in info inferiors: vfork relation no longer appears in info inferiors
new FAIL: gdb.base/foll-vfork.exp: exit: vfork parent follow, to bp: continue to bp
new FAIL: gdb.gdb/python-selftest.exp: call catch_command_errors(execute_command, "python print(5)", 0)
new FAIL: gdb.threads/fork-thread-pending.exp: 2, followed to the child, found two threads (GDB internal error)
PASS -> FAIL: gdb.threads/fork-thread-pending.exp: 2, get to the fork event
new FAIL: gdb.threads/fork-thread-pending.exp: 2, multiple threads found (GDB internal error)
PASS -> FAIL: gdb.threads/interrupted-hand-call.exp: continue until exit
============================


*** Failures that are being ignored ***
============================
FAIL: gdb.base/random-signal.exp: stop with control-c (timeout)
FAIL: gdb.dwarf2/gdb-index.exp: touch binary
FAIL: gdb.threads/next-bp-other-thread.exp: schedlock=off: next over function call============================




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