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

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0a0cb7e3237cf7bfec01b26b9ab4f52f1791ec7c

commit 0a0cb7e3237cf7bfec01b26b9ab4f52f1791ec7c
Author: Andrew Burgess <[email protected]>
Date:   Mon Jun 1 11:32:53 2026 +0100

    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:
---
 gdb/testsuite/gdb.python/py-frame.exp | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

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
 }