[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GC and stack marking
|
From: |
Stefan Monnier |
|
Subject: |
Re: GC and stack marking |
|
Date: |
Tue, 20 May 2014 23:01:24 -0400 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) |
> That's how I found out that it was being marked by mark_stack. But
> that doesn't tell you how that value _got_ on the stack, does it?
No, but it does tell you its address in the stack, so you can then walk
up the backtrace and look at the address of local variables until you
(hopefully) find the one that matters.
Stefan
- Re: GC and stack marking, (continued)
Re: GC and stack marking, Stefan Monnier, 2014/05/20
- Re: GC and stack marking, Eli Zaretskii, 2014/05/20
- Re: GC and stack marking, Stefan Monnier, 2014/05/20
- Re: GC and stack marking, Eli Zaretskii, 2014/05/20
- Re: GC and stack marking, Stefan Monnier, 2014/05/20
- Re: GC and stack marking, Eli Zaretskii, 2014/05/20
- Re: GC and stack marking,
Stefan Monnier <=
- Re: GC and stack marking, Eli Zaretskii, 2014/05/21
- Re: GC and stack marking, Dmitry Antipov, 2014/05/21
- Re: GC and stack marking, Dmitry Antipov, 2014/05/21
- Re: GC and stack marking, Eli Zaretskii, 2014/05/21
- Re: GC and stack marking, Eli Zaretskii, 2014/05/21
Re: GC and stack marking, Stefan Monnier, 2014/05/21
Re: GC and stack marking, Eli Zaretskii, 2014/05/21
Re: GC and stack marking, Eli Zaretskii, 2014/05/22
Re: GC and stack marking, Stefan Monnier, 2014/05/22
Re: GC and stack marking, Eli Zaretskii, 2014/05/24