Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master

[sergiodj+buildbot at redhat dot com]

Buildslave:
	wildebeest-debian-wheezy-x86_64

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

Commit(s) tested:
	cbb8991cabdd85b7828f59c92f754c5a2101b0b6

Author(s) (in the same order as the commits):
	Don Breazeal <donb@codesourcery.com>

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=51ccbcd4d6ebbab6466d258a05df528b68efc189>

*** Regressions found ***
============================
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
new 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
PASS -> FAIL: gdb.base/multi-forks.exp: follow parent, print pids
new FAIL: gdb.threads/fork-thread-pending.exp: 1, followed to the child, found two threads (GDB internal error)
new FAIL: gdb.threads/fork-thread-pending.exp: 1, get to the spawned thread in fork child (the program is no longer running)
new FAIL: gdb.threads/fork-thread-pending.exp: 1, multiple threads found (GDB internal error)
new FAIL: gdb.threads/fork-thread-pending.exp: 1, refused to resume (the program is no longer running)
new FAIL: gdb.threads/fork-thread-pending.exp: 1, switched away from event thread (GDB internal error)
new FAIL: gdb.threads/fork-thread-pending.exp: metest (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
PASS -> FAIL: gdb.base/multi-forks.exp: follow parent, print pids
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: 1, followed to the child, found two threads (GDB internal error)
new FAIL: gdb.threads/fork-thread-pending.exp: 1, get to the fork event
new FAIL: gdb.threads/fork-thread-pending.exp: 1, multiple threads found (GDB internal error)
new FAIL: gdb.threads/fork-thread-pending.exp: 1, switched away from event thread (GDB internal error)
new FAIL: gdb.threads/fork-thread-pending.exp: metest (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============================