[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: allocate_string_data memory corruption
From: |
Eli Zaretskii |
Subject: |
Re: allocate_string_data memory corruption |
Date: |
Thu, 19 Jan 2006 06:36:55 +0200 |
> Cc: address@hidden
> From: Chong Yidong <address@hidden>
> Date: Wed, 18 Jan 2006 18:48:58 -0500
>
> > Btw, does the value of `data' itself change in any way? You didn't
> > show its value at the offending line.
>
> `data' is just a variable, stored on the stack, that points to the
> next free region of memory in current_sblock (b->next_free). I
> haven't considered the possibility that `data' itself could have
> changed. I'll look into it.
If `data' is on the stack, perhaps it's changed by some ``no-op'' code
that smashes the stack.
- Re: allocate_string_data memory corruption, (continued)
- Re: allocate_string_data memory corruption, Ken Raeburn, 2006/01/18
- Re: allocate_string_data memory corruption, Chong Yidong, 2006/01/18
- Re: allocate_string_data memory corruption, Romain Francoise, 2006/01/19
- Re: allocate_string_data memory corruption, Stefan Monnier, 2006/01/19
- Re: allocate_string_data memory corruption, Kim F. Storm, 2006/01/19
- Re: allocate_string_data memory corruption, Stefan Monnier, 2006/01/19
- Re: allocate_string_data memory corruption, Richard M. Stallman, 2006/01/20
- Re: allocate_string_data memory corruption, Chong Yidong, 2006/01/24
- Re: allocate_string_data memory corruption, Richard M. Stallman, 2006/01/25