[Bug guile/27806] free(): invalid pointer during gdb.ada/fixed_cmp.exp

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=27806

--- Comment #15 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=225bda24db9671e2087fda892f94141625836a40

commit 225bda24db9671e2087fda892f94141625836a40
Author: Tom de Vries <tdevries@suse.de>
Date:   Tue May 4 10:26:16 2021 +0200

    [gdb/guile] Don't allow libguile to change libgmp mem fns

    Since gdb commit 880ae75a2b7 "gdb delay guile initialization until
    gdbscm_finish_initialization" I'm running into:
    ...
    (gdb) print My_Var > 10.0^M
    free(): invalid pointer^M
    ERROR: GDB process no longer exists
    GDB process exited with wait status 5995 exp9 0 0 CHILDKILLED SIGABRT
SIGABRT
    UNRESOLVED: gdb.ada/fixed_cmp.exp: gnat_encodings=all: print My_Var > 10.0
    ...

    The problem is that both gdb and libguile try to set the libgmp memory
functions,
    and since the gdb commit the ones from libguile are effective, which
results
    in gdb freeing some memory in a way that is not compatible with the way
that
    memory was actually allocated.

    The fact that libguile tries to set the libgmp memory functions is a bug
which
    should be fixed starting version v3.0.6.

    Meanwhile, work around this in gdb by not allowing libguile to set the
libgomp
    memory functions.

    Tested on x86_64-linux.

    gdb/ChangeLog:

    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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.