gdb/testsuite: gdb.base/continue-all-already-running.exp: add fail if can't run to...
authorSimon Marchi <simon.marchi@polymtl.ca>
Mon, 7 Jun 2021 16:51:34 +0000 (12:51 -0400)
committerSimon Marchi <simon.marchi@polymtl.ca>
Mon, 7 Jun 2021 16:51:34 +0000 (12:51 -0400)
commitcfc75767cc276fb9e10c8239bb23c800a7f07e47
treed24ca6aa50df02fddc8617455596612473cf5164
parenta12a15e7c5ff9f3549dd185fa1acd5a9dddd001b
gdb/testsuite: gdb.base/continue-all-already-running.exp: add fail if can't run to main

While doing some changes, I managed to break this test in a way that
running to main didn't work.  However, it didn't produce any FAIL.  I
noticed because I diff'ed the results and saw some PASSes unexpectedly
disappear, but that's a bit fragile.  Add a fail in case this test fails
to run to main.  Ideally, I think that runto_main should by default
produce a FAIL when it fails (the opposite of the existing logic), but
that's a project of its own, so just fix this test for the moment.

gdb/testsuite/ChangeLog:

* gdb.base/continue-all-already-running.exp: Call fail if can't
run to main.

Change-Id: I84b816a126c92ac579ed5ebbe39b017bd5cb7096
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/continue-all-already-running.exp