[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Changes that should go into version 24.4
From: |
Eli Zaretskii |
Subject: |
Re: Changes that should go into version 24.4 |
Date: |
Sat, 22 Mar 2014 11:08:14 +0200 |
> Date: Fri, 21 Mar 2014 18:57:03 -0700
> From: Daniel Colascione <address@hidden>
>
> It doesn't make sense that we'd fault accessing a stack slot on an
> active frame: doing so might corrupt something later, sure, but that
> stack location is valid and touching it isn't going to cause an
> immediate SIGSEGV.
Crashes in mark_object usually have nothing to do with accessing a
stack slot per se. mark_object looks at the object type, and then
extracts a pointer to a C structure from it, and proceeds treating
that pointer as a valid pointer to a valid structure of that type. If
pointer it extracts is invalid, or points to something that is not a C
struct of the type mark_object expects, we will segfault trying to
interpret those.
- Changes that should go into version 24.4, Richard Stallman, 2014/03/21
- Re: Changes that should go into version 24.4, Daniel Colascione, 2014/03/21
- Re: Changes that should go into version 24.4,
Eli Zaretskii <=
- Re: Changes that should go into version 24.4, Richard Stallman, 2014/03/22
- Re: GC bug investigation, Richard Stallman, 2014/03/23
- Re: GC bug investigation, David Kastrup, 2014/03/23
- Re: GC bug investigation, Richard Stallman, 2014/03/24
- Re: GC bug investigation, Daniel Colascione, 2014/03/23
- Re: GC bug investigation, Andreas Schwab, 2014/03/23