aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2023-04-17 11:20:02 -0600
committerTom Tromey <tromey@adacore.com>2023-06-12 11:51:52 -0600
commit4adf3a4059b291364842678be17d4b62214bbdbd (patch)
tree23829bc49ae1c629815559062344bddfdb23ab77 /gdb
parent9f82823f8972fbd4bba0230b27828d87f0548cbc (diff)
downloadgdb-4adf3a4059b291364842678be17d4b62214bbdbd.zip
gdb-4adf3a4059b291364842678be17d4b62214bbdbd.tar.gz
gdb-4adf3a4059b291364842678be17d4b62214bbdbd.tar.bz2
Stop gdb in gnat_runtime_has_debug_info
gnat_runtime_has_debug_info starts a new gdb to do its work. However, it also leaves this gdb running, which can potentially confuse the calling test -- I encountered this when writing a new DAP test. This patch changes the proc to shut down gdb.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/testsuite/lib/ada.exp2
1 files changed, 2 insertions, 0 deletions
diff --git a/gdb/testsuite/lib/ada.exp b/gdb/testsuite/lib/ada.exp
index b728e3a..b4a93fa 100644
--- a/gdb/testsuite/lib/ada.exp
+++ b/gdb/testsuite/lib/ada.exp
@@ -204,5 +204,7 @@ gdb_caching_proc gnat_runtime_has_debug_info {} {
}
}
+ gdb_exit
+
return $has_debug_info
}