diff options
| author | Tom Tromey <tromey@adacore.com> | 2024-02-23 13:18:49 -0700 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2024-02-27 10:30:29 -0700 |
| commit | beadf912845c9c37c5afeadd77635950cf697d9f (patch) | |
| tree | 0aea9a41c267cefe709c06f72e878f229a58be1b /gdb/guile | |
| parent | 1eae7be116ddabb13b34d2c2e8e0dc13fbae2a0d (diff) | |
| download | binutils-beadf912845c9c37c5afeadd77635950cf697d9f.zip binutils-beadf912845c9c37c5afeadd77635950cf697d9f.tar.gz binutils-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/guile')
| -rw-r--r-- | gdb/guile/guile.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/gdb/guile/guile.c b/gdb/guile/guile.c index 30d1c72..f0db709 100644 --- a/gdb/guile/guile.c +++ b/gdb/guile/guile.c @@ -115,6 +115,7 @@ static const struct extension_language_ops guile_extension_ops = { gdbscm_initialize, gdbscm_initialized, + nullptr, gdbscm_eval_from_control_command, |