On Sun, 28 Sep 2003 11:10:46 +0200 (CEST), Akim Demaille wrote: > Maybe you could try > the m4 I installed again, since I had a couple of additional > initializations that were missing, and caused valgrind to barf. > (Same place, same name, different contents). I re-tested using the newer m4 on four of the machines from the original nine which I trialed. All four re-tests failed with the same errors as reported previously. On Sun, 28 Sep 2003 11:58:54 +0200 (CEST), Akim Demaille wrote: > Could you make the test case smaller? Yes, I can attempt to do so. There seem to be two different crashes, so this might require two separate test cases. > Are you sure all the tests were run with the modified m4? Yes, I feel confident that the modified m4 was used. On the machines for which I have root access, I deleted the old m4 and autoconf installations completely before installing the new ones. On the machines for which I do not have root access, I made sure that PATH mentioned the location of the modified m4 before any other directories, and even set M4 for safety. The Autoconf configure script reported that it detected the modified m4. -- ES