Fix gdb.base/print-file-var-main.c value check logic
authorPedro Alves <palves@redhat.com>
Mon, 9 Oct 2017 11:33:31 +0000 (12:33 +0100)
committerPedro Alves <palves@redhat.com>
Mon, 9 Oct 2017 11:33:31 +0000 (12:33 +0100)
commit5c9e4427a745e5e26fba320ecc62e4285b613e4f
tree11452b4f01a2d9cd3d7e8c87e4fc01d23b3e072c
parent76f361eb4934dcda0626517c311b34fbc92d09b9
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.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/print-file-var-main.c
gdb/testsuite/gdb.base/print-file-var.exp
This page took 0.039601 seconds and 4 git commands to generate.