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 - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html