Re: command and doco for valgrind

[Nick Roberts]

 > > Here's a patch for valgrind relating to my earlier message. Any comments?
 > 
 > This is IMHO a borderline case: not only do we document GDB-related
 > features in the Emacs manual, but we also document usage of another
 > program that might help debugging programs.  I dunno.

I got no postive feedback the valgrind users list either so I won't commit
this patch. If I can develop the idea further, I will re-post it. Thanks for
an honest reply.

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

Nick