dc9366eb05
Avoid putting unstable path names in test messages, in order to avoid spurious testrun result diffs like: [....] -PASS: gdb.base/break-fun-addr.exp: /home/pedro/gdb/test-build1/gdb/testsuite/outputs/gdb.base/break-fun-addr/break-fun-addr1: break *main +PASS: gdb.base/break-fun-addr.exp: /home/pedro/gdb/test-build2/gdb/testsuite/outputs/gdb.base/break-fun-addr/break-fun-addr1: break *main [....] gdb/ChangeLog: 2017-03-08 Pedro Alves <palves@redhat.com> * gdb.base/break-fun-addr.exp: Use $testfile1/$testfile2 for test prefix instead of $binfile1/$binfile2. * gdb.btrace/gcore.exp: Use "core" instead of unstable path name in test message. * gdb.python/py-completion.exp: Use "load python file" as test messages instead of unstable path names. |
||
---|---|---|
.. | ||
buffer-size.exp | ||
data.c | ||
data.exp | ||
delta.exp | ||
dlopen-dso.c | ||
dlopen.c | ||
dlopen.exp | ||
enable-running.c | ||
enable-running.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-only.S | ||
i686-tailcall.S | ||
instruction_history.S | ||
instruction_history.c | ||
instruction_history.exp | ||
multi-thread-step.c | ||
multi-thread-step.exp | ||
nohist.exp | ||
non-stop.c | ||
non-stop.exp | ||
reconnect.c | ||
reconnect.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-only.c | ||
tailcall-only.exp | ||
tailcall.c | ||
tailcall.exp | ||
tsx.c | ||
tsx.exp | ||
unknown_functions.c | ||
unknown_functions.exp | ||
vdso.c | ||
vdso.exp | ||
x86-tsx.S | ||
x86_64-record_goto.S | ||
x86_64-tailcall-only.S | ||
x86_64-tailcall.S |