gdb/testsuite: return after reporting a test unsupported
authorAndrew Burgess <aburgess@redhat.com>
Mon, 10 Jul 2023 11:05:21 +0000 (12:05 +0100)
committerAndrew Burgess <aburgess@redhat.com>
Mon, 10 Jul 2023 11:05:21 +0000 (12:05 +0100)
commit44c8334f4af5b9895d196077f23e20e15eff4c03
tree0a095ad6d33271e587fd8b68f61a0302e5bf3c8b
parent3f3ffaca04967511fa14b5cb6ee4cd1ae3802c39
gdb/testsuite: return after reporting a test unsupported

In this commit:

  commit 8bcead69665af3a9f9867cd34c3a1daf22120027
  Date:   Tue May 23 11:25:01 2023 +0100

      gdb/testsuite: add test for core file with a 0 pid

a new test gdb.arch/core-file-pid0.exp was added.  This test includes
a pre-generated core file for x86-64 and for other architectures the
test reports 'unsupported'.

However, after reporting 'unsupported' the test failed to perform an
early return, so the test would then carry on and try to actually
perform the test, which resulted in some TCL errors.

Fix this by returning after reporting the test unsupported.
gdb/testsuite/gdb.arch/core-file-pid0.exp