Re: GC crashes

[Nick Roberts]

 > > Please do -- I know there is a memory corruption issue somewhere but
 > > so far nobody's been able to identify under what circumstances they
 > > happen.
 > 
 > Somebody with a very fast machine with lots of RAM and lots of spare
 > time could try to run Emacs under Valgrind.

Have you actually tried this? I can't get it to work with Emacs and the
documentation says:

doco> Emacs is known not to work with Valgrind because Emacs has its own
doco> memory-management scheme. Emacs works fine if you build it using the
doco> standard malloc/free routines.

and this is what I get:

==2325== Invalid free() / delete / delete[]
==2325==    at 0x1B900335: free (vg_replace_malloc.c:153)
==2325==    by 0x81467B6: (within /usr/bin/emacs-21.2)
==2325==    by 0x8054A15: (within /usr/bin/emacs-21.2)
==2325==    by 0x80F1A38: (within /usr/bin/emacs-21.2)
==2325==  Address 0x82B92D0 is not stack'd, malloc'd or (recently) free'd
emacs: Memory exhausted--use M-x save-some-buffers RET

I think it has something to do with the way that temacs dumps out emacs.

Recently I downloaded Valgrind 2.2.0, and this now works with temacs where
previously (2.0.0) it ended with a segmentation fault.

This runs like a dog though, and you need either a supercomputer or a lot of
patience.

Nick