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:13:30 +0000	[thread overview]
Message-ID: <bug-27806-4717-erIC2ab1Qj@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 #7 from Tom de Vries <vries at gcc dot gnu.org> ---
I'm not seeing this problem on my openSUSE Leap 15.2 build, presumably because
it uses libguile-2.0.so.22, which didn't have this change yet:
...
@@ -237,19 +237,20 @@ finalize_bignum (void *ptr, void *data)
 static void *
 custom_gmp_malloc (size_t alloc_size)
 {
-  return scm_malloc (alloc_size);
+  return scm_gc_malloc_pointerless (alloc_size, "GMP");
 }
...

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

  parent reply	other threads:[~2021-04-30 14:13 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 [this message]
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
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-erIC2ab1Qj@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: link
Be 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).