From: Neil Jerram <INVALID.NOREPLY@gnu.org>
To: marco.maggi-ipsu@poste.it, Neil Jerram <neil@ossau.uklinux.net>,
bug-guile@gnu.org
Subject: [bug #21483] mandelbug whit GUILE_DEBUG_MALLOC
Date: Wed, 31 Oct 2007 00:31:13 +0000 [thread overview]
Message-ID: <20071031-003113.sv185.25568@savannah.gnu.org> (raw)
In-Reply-To:
URL:
<http://savannah.gnu.org/bugs/?21483>
Summary: mandelbug whit GUILE_DEBUG_MALLOC
Project: Guile
Submitted by: ossau
Submitted on: Wednesday 10/31/07 at 00:31
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
Ciao,
just for the record, because I think that it is
unlikely that I or someone will succeed in fixing it.
It appears to me that there
is a problem in 'scm_malloc_reregister()', file
"libguile/debug-memory.c", which is invoked by
'scm_gc_realloc()' only when Guile is compiled
with 'GUILE_DEBUG_MALLOC' defined.
It tells me that I am trying to reallocate a block
with a different "what" string.
It comes and goes, but for the small code
evolution span in which it was reproducible: I was
able to determine that I was using the same
"what".
I circumvented it, it seems, by using the same
"what" in two different invocations to
"scm_gc_realloc()".
Understanding what is going on requirers
understanding the hash table handling, which is
a little mess IMHO, and it is above my head now.
--
Marco Maggi
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?21483>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
reply other threads:[~2007-10-31 0:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071031-003113.sv185.25568@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=marco.maggi-ipsu@poste.it \
--cc=neil@ossau.uklinux.net \
/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).