|
From: Julian S. <js...@ac...> - 2004-12-06 10:16:22
|
On Monday 06 December 2004 09:59, Nicholas Nethercote wrote: > On Sun, 5 Dec 2004, Nick Roberts wrote: > > In the documentation for Valgrind, it states: > >> Emacs is known not to work with Valgrind because Emacs has its own > >> memory-management scheme. Emacs works fine if you build it using the > >> standard malloc/free routines. > > > > Could someone please clarify, more explicitly, what "build it using the > > standard malloc/free routines" entails? I've had varying success running GNU emacs on recent V's; one time it worked, but another time it didn't. I think it is to do with emacs doing something wildly non-portable with brk() and being confused by V's behaviour. xemacs doesn't have any such stupidness. "build it using the standard malloc/free routines" is just a ./configure option to emacs, IIRC. Something like --use-system-malloc -- you'll have to check, I don't really remember. Note I also have to use --with-x-toolkit=NONE in order to get a build of emacs which doesn't simply segfault at startup. J |