[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GC and stack marking
From: |
Eli Zaretskii |
Subject: |
Re: GC and stack marking |
Date: |
Wed, 21 May 2014 05:48:08 +0300 |
> From: Stefan Monnier <address@hidden>
> Cc: address@hidden, address@hidden
> Date: Tue, 20 May 2014 18:01:05 -0400
>
> > I tried, but couldn't. Suggestions for how to set up a GDB session
> > for that are welcome.
>
> I guess you could try the following:
> - interrupt the dump just before setting purify-flag to nil.
> - get the value of purify-flag.
> - set a conditional break point in mark_object that catches the case
> where the argument is equal to the value you just got.
> - "c"
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?
- 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 <=
- Re: GC and stack marking, Stefan Monnier, 2014/05/20
- 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