From: Andrew Burgess <aburgess@redhat.com>
Date: Mon, 1 Jun 2026 10:32:53 +0000 (+0100)
Subject: gdb/testsuite: don't overwrite test executable in py-frame.exp
X-Git-Tag: binutils-2_47~56
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0a0cb7e3237cf7bfec01b26b9ab4f52f1791ec7c;p=thirdparty%2Fbinutils-gdb.git

gdb/testsuite: don't overwrite test executable in py-frame.exp

In gdb.python/py-frame.exp when we re-compile the test executable
without debug information, give it a new, unique, name to make
re-running the tests outside the testsuite easier.

While I was in the area I removed a `gdb_exit` call that was not
necessary, `prepare_for_testing` calls `clean_restart` which already
does a `gdb_exit`.

There should be no change in what is being tested after this commit.
---

diff --git a/gdb/testsuite/gdb.python/py-frame.exp b/gdb/testsuite/gdb.python/py-frame.exp
index 6feb1392437..596d82e4fb4 100644
--- a/gdb/testsuite/gdb.python/py-frame.exp
+++ b/gdb/testsuite/gdb.python/py-frame.exp
@@ -204,8 +204,7 @@ gdb_test "python print(gdb.selected_frame().read_register(bad_object))" \
     "test Frame.read_register with bad_type object"
 
 # Compile again without debug info.
-gdb_exit
-if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile} {}] } {
+if { [prepare_for_testing "failed to prepare" ${testfile}-nodebug ${srcfile} {}] } {
     return
 }