diff options
| -rw-r--r-- | gdb/ChangeLog | 6 | ||||
| -rw-r--r-- | gdb/guile/guile.c | 16 |
2 files changed, 22 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 6ec6a70..674817c 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,9 @@ +2021-05-04 Tom de Vries <tdevries@suse.de> + + PR guile/27806 + * guile/guile.c (gdbscm_initialize): Don't let guile change libgmp + memory functions. + 2021-04-30 Tom Tromey <tom@tromey.com> * dwarf2/read.c (dwarf2_initialize_objfile): Update. diff --git a/gdb/guile/guile.c b/gdb/guile/guile.c index bdf15cd..c6959f5 100644 --- a/gdb/guile/guile.c +++ b/gdb/guile/guile.c @@ -662,6 +662,22 @@ gdbscm_initialize (const struct extension_language_defn *extlang) { gdb::block_signals blocker; + /* There are libguile versions (f.i. v3.0.5) that by default call + mp_get_memory_functions during initialization to install custom + libgmp memory functions. This is considered a bug and should be + fixed starting v3.0.6. + Before gdb commit 880ae75a2b7 "gdb delay guile initialization until + gdbscm_finish_initialization", that bug had no effect for gdb, + because gdb subsequently called mp_get_memory_functions to install + its own custom functions in _initialize_gmp_utils. However, since + aforementioned gdb commit the initialization order is reversed, + allowing libguile to install a custom malloc that is incompatible + with the custom free as used in gmp-utils.c, resulting in a + "double free or corruption (out)" error. + Work around the libguile bug by disabling the installation of the + libgmp memory functions by guile initialization. */ + scm_install_gmp_memory_functions = 0; + /* scm_with_guile is the most portable way to initialize Guile. Plus we need to initialize the Guile support while in Guile mode (e.g., called from within a call to scm_with_guile). */ |