aboutsummaryrefslogtreecommitdiff
path: root/gdb/top.c
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2024-02-23 13:18:49 -0700
committerTom Tromey <tromey@adacore.com>2024-02-27 10:30:29 -0700
commitbeadf912845c9c37c5afeadd77635950cf697d9f (patch)
tree0aea9a41c267cefe709c06f72e878f229a58be1b /gdb/top.c
parent1eae7be116ddabb13b34d2c2e8e0dc13fbae2a0d (diff)
downloadgdb-beadf912845c9c37c5afeadd77635950cf697d9f.zip
gdb-beadf912845c9c37c5afeadd77635950cf697d9f.tar.gz
gdb-beadf912845c9c37c5afeadd77635950cf697d9f.tar.bz2
Add extension_language_ops::shutdown
Right now, Python is shut down via a final cleanup. However, it seems to me that it is better for extension languages to be shut down explicitly, after all the ordinary final cleanups are run. The main reason for this is that a subsequent patch adds another case like finalize_values; and rather than add a series of workarounds for Python shutdown, it seemed better to let these be done via final cleanups, and then have Python shutdown itself be the special case.
Diffstat (limited to 'gdb/top.c')
-rw-r--r--gdb/top.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/gdb/top.c b/gdb/top.c
index 5114713..67d6670 100644
--- a/gdb/top.c
+++ b/gdb/top.c
@@ -1819,6 +1819,8 @@ quit_force (int *exit_arg, int from_tty)
exception_print (gdb_stderr, ex);
}
+ ext_lang_shutdown ();
+
exit (exit_code);
}