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

[Andrew Burgess <aburgess@redhat.com>]

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.
---
 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 ca350cf03c2..9c425f6aa98 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
 }
 
-- 
2.25.4