binutils-gdb/gdb/testsuite/gdb.btrace
Markus Metzger abcef95aa5 btrace, test: avoid gdb.btrace/vdso.exp fail
The vdso.exp test checks that we can access the VDSO memory when replaying.

Depending on the line information generated by the compiler, runto_main may run
to the line marked with bp.1 or stop before that line.  The test incorrectly
assumes that it will always run to the marked line and fails if it doesn't.

The test does not really care about what is traced.  It does care that GDB is
replaying when capturing the second disassemble output.

Reflect that in the test by ignoring the output of the stepping and record goto
begin commands and by checking that GDB is actually replaying.

testsuite/
	* gdb.btrace/vdso.c (main): Remove breakpoint markers.
	* gdb.btrace/vdso.exp: Change stepping command to "next" and ignore
	its output.  Ignore the output of "record goto begin" and instead
	check that GDB is replaying.
2015-10-09 14:29:41 +02:00
..
Makefile.in
buffer-size.exp
data.c
data.exp
delta.exp
enable.c
enable.exp
exception.cc
exception.exp
function_call_history.c
function_call_history.exp
gcore.exp
i686-record_goto.S
i686-tailcall.S
instruction_history.S
instruction_history.c
instruction_history.exp
multi-thread-step.c
multi-thread-step.exp btrace: honour scheduler-locking for all-stop targets 2015-09-18 14:33:16 +02:00
nohist.exp
non-stop.c
non-stop.exp
record_goto-step.exp
record_goto.c
record_goto.exp
rn-dl-bind.c
rn-dl-bind.exp
segv.c
segv.exp
step.exp
stepi.exp
tailcall.c
tailcall.exp
tsx.c
tsx.exp btrace, testsuite: fix spurious gdb.btrace/tsx.exp fails 2015-09-30 14:48:38 +02:00
unknown_functions.c
unknown_functions.exp
vdso.c btrace, test: avoid gdb.btrace/vdso.exp fail 2015-10-09 14:29:41 +02:00
vdso.exp btrace, test: avoid gdb.btrace/vdso.exp fail 2015-10-09 14:29:41 +02:00
x86-tsx.S
x86_64-record_goto.S
x86_64-tailcall.S