On Sun, Apr 27, 2003 at 05:53:13PM +0200, [EMAIL PROTECTED] wrote: > On Sun, Apr 27, 2003 at 08:48:11AM +0200, Olivier Chapuis wrote: > > On Sun, Apr 27, 2003 at 02:09:48AM +0200, [EMAIL PROTECTED] wrote: > > > Olivier, how did get Valgrind to produce any usable output? When > > > I run it (after compiling with -O), it swaps me in "uninitialised > > > memory" messages all over the place when they are clearly wrong, > > > e.g. in the flag structures and the new exec_context_t structures, > > > even when both were initialised with memset or safecalloc. For me > > > it is almost impossible to distinguish the real problems from the > > > junk reports. > > > > > > > Yes, I've noted problems with UM too. It seems that the latest valgrind > > version (I get it from valgrind cvs) is better regarding this. > > URL? I can't find the cvs repository. >
Valgrind devel site: https://sourceforge.net/projects/valgrind for the cvs as usual on sf: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/valgrind login cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/valgrind co valgrind Regards, Olivier -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
