Re: valgrind warnings [Re: Emacs bzr memory footprint]

[Andreas Schwab]

Chong Yidong <address@hidden> writes:

> Dan Nicolaescu <address@hidden> writes:
>
>>> ==30382== Use of uninitialised value of size 8
>>> ==30382==    at 0x5B7000: mark_object (alloc.c:5674)
>>> ==30382==    by 0x5B4C9B: mark_maybe_object (alloc.c:4152)
>>> ==30382==    by 0x5B4FE6: mark_memory (alloc.c:4274)
>>> ==30382==    by 0x5B507E: mark_stack (alloc.c:4532)
>>> ==30382==    by 0x5B5F48: Fgarbage_collect (alloc.c:5119)
>>> ==30382==    by 0x5D69F0: Ffuncall (eval.c:2911)
>>> ==30382==    by 0x5D64CA: call2 (eval.c:2758)
>>> ==30382==    by 0x5809AA: Finsert_file_contents (fileio.c:4144)
>>> ==30382==    by 0x5D6E00: Ffuncall (eval.c:2990)
>>> ==30382==    by 0x622C5B: exec_byte_code (bytecode.c:785)
>>> ==30382==    by 0x5D77BA: funcall_lambda (eval.c:3205)
>>> ==30382==    by 0x5D6F4C: Ffuncall (eval.c:3023)
>>
>> It would be interesting to know if the gc warnings are relevant...
>
> This is complaining about the plist member of struct Lisp_Overlay, but I
> don't see how an uninitalized value could creep in there.  Overlays are
> only allocated in copy_overlays and Fmake_overlay, and in both places
> the plist member appears to be assigned correctly.

This is while scanning the stack, where it is apparently possible that
this happens to look like a Lisp_Object, but isn't.

Andreas.

-- 
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."