From: ludo@gnu.org (Ludovic Courtès)
To: 9900@debbugs.gnu.org
Subject: bug#9900: local vars not cleaned
Date: Tue, 01 Nov 2011 01:20:34 +0100 [thread overview]
Message-ID: <87wrbkg0bx.fsf@gnu.org> (raw)
In-Reply-To: <m3mxckvoe2.fsf@Kagami.home>
Hi Stefan,
Stefan Israelsson Tampe <stefan.itampe@gmail.com> skribis:
> A program is executed and a set of locals is allocated on the stack for the
> duration of the loading, this means that during the
> whole execution of the loaded file the locals variables are below the stack
> pointer and hence always contains a reference from the stack to the last
> used objects in the local variables.
Normally the GC will only scan the relevant part of the VM stack–see
‘VM_ENABLE_PRECISE_STACK_GC_SCAN’ in vm.c. If you think this is not
working as advertised, can you add a breakpoint in ‘vm_stack_mark’ and
see what happens?
To check your hypothesis you could also define ‘VM_ENABLE_STACK_NULLING’
in vm.c.
TIA! :-)
Ludo’.
next prev parent reply other threads:[~2011-11-01 0:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 20:42 bug#9900: Using a guardian on a value in a weak hash Ian Price
2011-10-29 17:42 ` Stefan Israelsson Tampe
2011-10-29 18:51 ` Ian Price
2011-10-30 13:52 ` bug#9900: local vars not cleaned Stefan Israelsson Tampe
2011-10-30 18:49 ` Stefan Israelsson Tampe
2011-11-01 0:20 ` Ludovic Courtès [this message]
2011-11-01 19:53 ` Andy Wingo
2011-11-09 22:47 ` bug#9900: Using a guardian on a value in a weak hash Andy Wingo
2011-12-14 21:49 ` Ludovic Courtès
2011-12-15 21:55 ` Andy Wingo
2011-12-18 23:38 ` Ludovic Courtès
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=87wrbkg0bx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=9900@debbugs.gnu.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).