diff options
| author | Markus Metzger <markus.t.metzger@intel.com> | 2015-09-30 11:41:35 +0200 |
|---|---|---|
| committer | Markus Metzger <markus.t.metzger@intel.com> | 2015-10-09 14:29:41 +0200 |
| commit | abcef95aa511a845f0599178be09403348ba4bad (patch) | |
| tree | 053952f5cb12414361eae310f7263edfe2e78d9f /gdb/gcore.in | |
| parent | 145e3ddb4b1657a1f29eb9f41f2d54d0bf26b6f0 (diff) | |
| download | fsf-binutils-gdb-abcef95aa511a845f0599178be09403348ba4bad.zip fsf-binutils-gdb-abcef95aa511a845f0599178be09403348ba4bad.tar.gz fsf-binutils-gdb-abcef95aa511a845f0599178be09403348ba4bad.tar.bz2 | |
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.
Diffstat (limited to 'gdb/gcore.in')
0 files changed, 0 insertions, 0 deletions