diff options
| author | Simon Marchi <simon.marchi@efficios.com> | 2021-06-17 09:41:58 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@polymtl.ca> | 2021-06-17 09:41:58 -0400 |
| commit | c4ddc1daef6e5f640500655dde6bb1acad13c38a (patch) | |
| tree | 0013218afd6936288924dafccb2d00fe5e987bab /contrib | |
| parent | 18b5aadea2de6955ba5818c65ef82c94c6ca5d98 (diff) | |
| download | gdb-c4ddc1daef6e5f640500655dde6bb1acad13c38a.zip gdb-c4ddc1daef6e5f640500655dde6bb1acad13c38a.tar.gz gdb-c4ddc1daef6e5f640500655dde6bb1acad13c38a.tar.bz2 | |
gdb/testsuite: gdb.base/args.exp: use $old_gdbflags last two tests
All tests in this file append to GDBFLAGS instead of overwriting it,
except the last two. I noticed because when testing with the
native-extended-remote board, it removes the "set sysroot" argument, and
it causes the test to be very long to run, due to big glibc debug info
being read through the remote target.
I think this oddity is due to a race condition between these two
commits:
[1] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=c22261528c50f7760dd6a2e29314662b377eebb4
[2] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6b8ce727297b1e40738e50f83a75881b290fe6a6
The first one added the two tests. The second one changes the test to
append to GDBFLAGS instead of overwriting it. But the second one was
probably written before the first one was it, so missed the new tests.
Change those two tests to be like the others.
gdb/testsuite/ChangeLog:
* gdb.base/args.exp: Use $old_gdbflags in all tests.
Change-Id: I531276125ecb70e80f52adbd320ebb85b0c8eba0
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions