[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Nasty GC bug

From: Dmitry Antipov
Subject: Re: Nasty GC bug
Date: Fri, 24 Aug 2012 14:58:18 +0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120713 Thunderbird/14.0

On 08/24/2012 12:56 PM, Paul Eggert wrote:

Thanks for finding this bug.

That patch doesn't look quite right if ! USE_LSB_TAG, since
in that case lisp_align_malloc won't correctly report a
failure in the section of code that checks whether the
memory just allocated can be addressed through a Lisp
object's pointer.  Also, what about dont_register_blocks
and allocated_mem_type?

Instead, how about marking the spare conses with Vdead
and the spare strings with NULL data?  Admittedly I
haven't had time to think this through....

This implies initialization of the data which we will never
use; what about the special memory type, e.g. MEM_TYPE_SPARE?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]