Re: command and doco for valgrind

[Eli Zaretskii]

> Date: Sat, 17 Jan 2004 23:38:58 +0000
> From: Nick Roberts <address@hidden>
> 
> BTW I think valgrind could be a useful tool to debug some of Emacs crashes
> (less frequent now) on x86 architectures. However, for some reason, it reports
> a memory full message at start up, at the moment:
> 
> ==2466== Invalid free() / delete / delete[]
> ==2466==    at 0x400263A8: free (vg_replace_malloc.c:231)
> ==2466==    by 0x812A135: memory_full (alloc.c:478)
> ==2466==    by 0x812A3E8: lisp_malloc (alloc.c:623)
> ==2466==    by 0x812BA07: allocate_vectorlike (alloc.c:2505)
> ==2466==    Address 0x83CCE60 is not stack'd, malloc'd or free'd
> emacs: Memory exhausted--use M-x save-some-buffers then exit and restart Emacs

I suspect that it has something to do with the dumping process (which
effectively freezes memory malloc'ed before unexec), but I don't know
enough about valgrind to tell for sure.