public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27806] free(): invalid pointer during gdb.ada/fixed_cmp.exp Date: Fri, 30 Apr 2021 14:56:03 +0000 [thread overview] Message-ID: <bug-27806-4717-HEq9E0Zo50@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27806-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27806 --- Comment #13 from Tom de Vries <vries at gcc dot gnu.org> --- Well, this works: ... diff --git a/gdb/guile/guile.c b/gdb/guile/guile.c index 9c2a40b61be..71e74892ab3 100644 --- a/gdb/guile/guile.c +++ b/gdb/guile/guile.c @@ -664,10 +664,19 @@ gdbscm_finish_initialization (const struct extension_langua ge_defn *extlang) { gdb::block_signals blocker; + /* Save libgmp memory functions. */ + void *(*alloc_func) (size_t); + void *(*realloc_func) (void *, size_t, size_t); + void (*free_func) (void *, size_t); + mp_get_memory_functions (&alloc_func, &realloc_func, &free_func); + /* 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). */ scm_with_guile (call_initialize_gdb_module, NULL); + + /* Restore libgmp memory functions. */ + mp_set_memory_functions (alloc_func, realloc_func, free_func); } /* Set Guile's backtrace to match the "set guile print-stack" default. ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-30 14:56 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-30 12:49 [Bug gdb/27806] New: " vries at gcc dot gnu.org 2021-04-30 12:50 ` [Bug gdb/27806] " vries at gcc dot gnu.org 2021-04-30 12:52 ` vries at gcc dot gnu.org 2021-04-30 13:19 ` vries at gcc dot gnu.org 2021-04-30 13:48 ` vries at gcc dot gnu.org 2021-04-30 14:00 ` vries at gcc dot gnu.org 2021-04-30 14:09 ` simark at simark dot ca 2021-04-30 14:13 ` vries at gcc dot gnu.org 2021-04-30 14:26 ` vries at gcc dot gnu.org 2021-04-30 14:29 ` vries at gcc dot gnu.org 2021-04-30 14:35 ` vries at gcc dot gnu.org 2021-04-30 14:37 ` simark at simark dot ca 2021-04-30 14:42 ` vries at gcc dot gnu.org 2021-04-30 14:56 ` vries at gcc dot gnu.org [this message] 2021-05-03 8:39 ` [Bug guile/27806] " vries at gcc dot gnu.org 2021-05-03 8:55 ` vries at gcc dot gnu.org 2021-05-04 8:26 ` cvs-commit at gcc dot gnu.org 2021-05-04 8:28 ` vries at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-27806-4717-HEq9E0Zo50@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).