diff options
author | Pedro Alves <palves@redhat.com> | 2013-03-26 18:26:05 +0000 |
---|---|---|
committer | Pedro Alves <palves@redhat.com> | 2013-03-26 18:26:05 +0000 |
commit | 12bcab2df52ecd5f129effe097084439334dcd98 (patch) | |
tree | d8242b3f19cb0d4ac85898e8124a5a719baa42da /config/gettext.m4 | |
parent | eaae37beaf518a830507c48e08cf697b1906f7b9 (diff) | |
download | gdb-12bcab2df52ecd5f129effe097084439334dcd98.tar.gz |
Get rid of "No such file or directory" in the testsuite's btrace support detection.
When I tried running the btrace tests, I noticed something odd in the gdb.log file:
(gdb) run
Starting program: /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.btrace/btrace22343.x
Breakpoint 1, main () at /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.btrace/btrace22343.c:1
1 /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.btrace/btrace22343.c: No such file or directory.
^^^^^^^^^^^^^^^^^^^^^^^^^
(gdb) record btrace
Target does not support branch tracing.
(gdb) testcase ../../../src/gdb/testsuite/gdb.btrace/enable.exp completed in 0 seconds
I knew that the btrace tests on my machine weren't supposed to work,
but still, that error made me wonder if the test had something broken,
and waste a few minutes looking up where that is coming from.
The issue is that the btrace detection deletes the source file right
after compiling it, and before GDB has a chance to open it. It's
really harmless, but I'd rather spare others from going through the
same exercise.
We now get the regular:
(gdb) run
Starting program: /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.btrace/btrace24210.x
...
Breakpoint 1, main () at /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.btrace/btrace24210.c:1
1 int main(void) { return 0; }
...
gdb/testsuite/
2013-03-26 Pedro Alves <palves@redhat.com>
* lib/gdb.exp (skip_btrace_tests): Delay deleting the source file
until after GDB has run.
Diffstat (limited to 'config/gettext.m4')
0 files changed, 0 insertions, 0 deletions