diff options
| author | Pedro Alves <palves@redhat.com> | 2017-10-09 12:33:31 +0100 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2017-10-09 12:33:31 +0100 |
| commit | 5c9e4427a745e5e26fba320ecc62e4285b613e4f (patch) | |
| tree | 11452b4f01a2d9cd3d7e8c87e4fc01d23b3e072c /gdb/breakpoint.c | |
| parent | 76f361eb4934dcda0626517c311b34fbc92d09b9 (diff) | |
| download | binutils-5c9e4427a745e5e26fba320ecc62e4285b613e4f.zip binutils-5c9e4427a745e5e26fba320ecc62e4285b613e4f.tar.gz binutils-5c9e4427a745e5e26fba320ecc62e4285b613e4f.tar.bz2 | |
Fix gdb.base/print-file-var-main.c value check logic
Fix a typo introduced in commit c56e7c4390ed ("Make ctxobj.exp and
print-file-var.exp work on all platforms.").
This doesn't really affect the outcome of the testcase. I only
noticed the typo because I stepped through the program manually.
To avoid such problems if the test is extended, this moves the STOP
marker until after the program self-validates the values. With the
typo in place, this alone would have resulted in a test FAIL. I.e.,
it'd have caught the typo.
gdb/testsuite/ChangeLog:
2017-10-09 Pedro Alves <palves@redhat.com>
* gdb.base/print-file-var-main.c: Fix get_version_2 value check
logic. Move STOP marker after the value checks.
* gdb.base/print-file-var.exp (continue to STOP marker): Tighten
regexp.
Diffstat (limited to 'gdb/breakpoint.c')
0 files changed, 0 insertions, 0 deletions