* Ben Wing <ben(a)666.com&gt; writes: > Have you tried using run-temacs? Fabrice Popineau wrote: I have succeded in running temacs under BoundsChecker and dumping xemacs from there. Some strange things have been reported (I can be more precise if needed) about some memory blocks overwritten. However, emacs is doing clever things and it may happen that BoundsChecker be fooled. The most annoying problem is that it is almost impossible to run xemacs from BoundsChecker : the program is instrumended at ath win32 api level while running and is far too slow. I might try it on a faster machine in a few days, but this is a serious problem. It is a pity because BoundsChecker has proven ti be very useful in tracking resources leaks in the past. All this has been triggered by Adrian Aichner telling me that something like 'M-x compile' then 'dir' will result in a leak of 2 handles (xemacs 21.2beta24, native win32). Any hint / suggestion /comment welcome, Fabrice Popineau