From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: plugged a memleak
Date: Fri, 23 Mar 2012 19:03:19 +0100 [thread overview]
Message-ID: <87fwcz9ouw.fsf@gnu.org> (raw)
In-Reply-To: <877gydoblm.fsf@pobox.com> (Andy Wingo's message of "Wed, 21 Mar 2012 23:03:49 +0100")
Hi,
Andy Wingo <wingo@pobox.com> skribis:
> On Wed 21 Mar 2012 22:02, ludo@gnu.org (Ludovic Courtès) writes:
>
>>> See c05805a4ea764dec5a0559edefcdfb9761191d07 in stable-2.0 for the
>>> gnarly details. The summary is that applicable smobs were being leaked,
>>> because they were referenced in the values of weak-key tables.
>>
>> I was wondering whether removing ‘smob-call’ would break binary
>> compatibility, but presumably that instruction could not possibly end up
>> in user bytecode on disk, right?
>
> Presumably not. It is documented, though. We can remove it, but its
> continued presence doesn't cost us anything. I'm OK with either option
Right, we can leave it.
Thanks!
Ludo’.
prev parent reply other threads:[~2012-03-23 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 20:20 plugged a memleak Andy Wingo
2012-03-21 21:02 ` Ludovic Courtès
2012-03-21 22:03 ` Andy Wingo
2012-03-23 18:03 ` Ludovic Courtès [this message]
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=87fwcz9ouw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).