testsuite: Fix save-trace.exp writing outside standard output directory
authorSimon Marchi <simon.marchi@ericsson.com>
Tue, 16 Feb 2016 14:00:50 +0000 (09:00 -0500)
committerSimon Marchi <simon.marchi@ericsson.com>
Tue, 16 Feb 2016 14:01:38 +0000 (09:01 -0500)
commit266b65b33e23c916e5e698d24c37f65d90645a19
treedf74af17b50ad4ed32b8f78adf2bc1d24e20b3a9
parent1cd17042aad6b0c2e10537bb400a496958178029
testsuite: Fix save-trace.exp writing outside standard output directory

In save-trace.exp, we want to test loading of a tracepoint definition
file with a relative path (I am not sure why in fact).  We currently use
"savetrace-relative.tr", which ends up directly in testsuite/.  If we
use [standard_output_file] on that path, it becomes absolute.  I decided
to just replace [pwd] with . (a dot) in the path given by
standard_output_file to make it relative.  However, this trick only
works because [pwd] is a prefix of the standard output directory.  So I
added a check to verify that precondition.

gdb/testsuite/ChangeLog:

* gdb.trace/save-trace.exp: Change relative path to be in the
standard output directory.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.trace/save-trace.exp