[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GC and stack marking
|
From: |
Barry OReilly |
|
Subject: |
Re: GC and stack marking |
|
Date: |
Wed, 21 May 2014 15:31:49 -0400 |
> It might simply be a slot that's unused by the current stack frame,
> whose value comes from some stack frame that existed some time in
> the past.
So should the relevant C code try to initialize variables with non
garbage? I took a look at Fgarbage_collect and found that the
stack_top_variable variable for example is garbage valued.
Re: GC and stack marking, Florian Weimer, 2014/05/31
Re: GC and stack marking,
Barry OReilly <=
- Re: GC and stack marking, Eli Zaretskii, 2014/05/21
- Re: GC and stack marking, Barry OReilly, 2014/05/21
- Re: GC and stack marking, Eli Zaretskii, 2014/05/21
- Re: GC and stack marking, Daniel Colascione, 2014/05/21
- Re: GC and stack marking, David Kastrup, 2014/05/22
- Re: GC and stack marking, Stefan Monnier, 2014/05/22
- Re: GC and stack marking, Eli Zaretskii, 2014/05/22
Re: GC and stack marking, Barry OReilly, 2014/05/22
Re: GC and stack marking, Eli Zaretskii, 2014/05/22