Re: GC and stack marking

[Stefan Monnier]

> I already tried that before, and came up empty-handed.  I tried again
> now; the address of that value on the stack does not correspond to any
> local variable in the corresponding stack frame, and I also cannot
> find that address in the disassembly of the function whose stack frame
> includes the value.

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.

Which stack frame is that?  Is it high up or very deep (both of which
we could hope to solve by using tighter bounds on the start and end
addresses of the stack scan), or neither?

> Now, I have a question: mark_stack stops examining the stack when it
> gets to its own stack frame.  That is certainly safe, but it sounds
> too conservative: it should stop at the stack frame of
> Fgarbage_collect, I think, because no live Lisp object can appear
> while Fgarbage_collect runs, right?

Sounds right, yes.


        Stefan