git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Running parse cvs

From
Linus Torvalds <torvalds@osdl.org>
Date
Jun 16, 2006, 19:24 UTC
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
Previous: Jon SmirlNext: Johannes Schindelin
Message 3 of 4 in “Running parse cvs”
  1. Jon SmirlJun 16, 2006
  2. Jon SmirlJun 16, 2006
  3. Linus TorvaldsJun 16, 2006
  4. Johannes SchindelinJun 16, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.