[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: |
Tue, 20 May 2014 22:28:48 +0300 |
> From: Stefan Monnier <address@hidden>
> Cc: address@hidden, address@hidden
> Date: Tue, 20 May 2014 13:54:16 -0400
>
> >> But it shouldn't cause any trouble (other than extra memory use).
> > It does, due to all kinds of subtleties. The result is that the
> > large_vectors linked list gets dumped with a pointer to a non-existent
> > memory, and the dumped Emacs then crashes on the first GC when it
> > tries to traverse that linked list.
>
> We should fix that.
No argument here. Otherwise the dumped Emacs crashes.
> > I think this is hopeless: I see this problem on a single system; two
> > others don't have it. It's just some semi-random garbage somehwre on
> > the stack.
>
> Of course, but if you can find where it comes from, we can fix that
> one case.
I tried, but couldn't. Suggestions for how to set up a GDB session
for that are welcome.
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/20
- 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