From: Linus Torvalds <torvalds@osdl.org>
Date: Fri, 16 Jun 2006 19:24:07 GMT
Subject: Re: Running parse cvs
Message-ID: <Pine.LNX.4.64.0606161220360.5498@g5.osdl.org>
In-Reply-To: <9e4733910606161147m403a3f36r6657bd7b620958f3@mail.gmail.com>



On Fri, 16 Jun 2006, Jon Smirl wrote:
>
> I am running the latest parsecvs from your git tree. I am hitting a quick gpf.

If it's really quick, run it under valgrind. It will slow down things 
enormously, but if it happens early on, you won't care, and it will 
generally give a much better reason for why the problem happened than the 
glibc malloc debugger will.

Ie just

	valgrind --tool=memcheck parsecvs ..

should do it.

Valgrind is da bomb.

		Linus