Some time ago, Ben Wing wrote...
if you trace through the gmalloc code and you find one location
that's
definitely
gotten trashed, try setting a watch point (i.e. break on write) on that
particular location. if you're lucky, this will pinpoint exactly who's
trashing
that location.
Andy,
I can build XEmacs with MSVC using debug memory allocator, kind of
purify thing. If you can supply the exact test sequence which you
suspect trashes memory, then I can run it with that build, to see
where exactly does it occur.
I guess I should make the debug allocator the default when USE_
SYSTEM_MALLOC and DEBUG_XEMACS are both defined.
Big K