diff options
| author | Yao Qi <yao@codesourcery.com> | 2014-04-02 12:44:22 +0800 |
|---|---|---|
| committer | Yao Qi <yao@codesourcery.com> | 2014-04-11 12:54:09 +0800 |
| commit | 322f9c2100806387b8ace4df7a2b940b03b3d703 (patch) | |
| tree | 4acbea5f32c3220c475dac58bdc05496fbce1d28 /gdb/stabsread.c | |
| parent | 1511baeca965fcf4cf36379c6b3f8a0b85263544 (diff) | |
| download | gdb-322f9c2100806387b8ace4df7a2b940b03b3d703.zip gdb-322f9c2100806387b8ace4df7a2b940b03b3d703.tar.gz gdb-322f9c2100806387b8ace4df7a2b940b03b3d703.tar.bz2 | |
Check file exists before completion tests
Doug told me that there are some regressions in gdb.base/completion.exp.
They are caused by my recent change, and can be reproduced via:
$ make check-parallel TESTS=gdb.base/completion.exp
FAIL: gdb.base/completion.exp: complete target core ./gdb.base/completion
FAIL: gdb.base/completion.exp: complete target tfile ./gdb.base/completion
FAIL: gdb.base/completion.exp: complete target exec ./gdb.base/completion
Current tests assume that gdb.base/completion exists but that is wrong
in a parallel run, because binary file and object files are placed
in outputs/gdb.base/completion/.
This patch is to check file exists on two candidate directories,
"gdb.base" and "outputs/gdb.base/completion/", and run tests with files
existed in either of them.
gdb/testsuite:
2014-04-11 Yao Qi <yao@codesourcery.com>
* gdb.base/completion.exp: Check file exists before running tests
on file completion.
Diffstat (limited to 'gdb/stabsread.c')
0 files changed, 0 insertions, 0 deletions