threads / discuss / 4534

Running parse cvs

Subject: Running parse cvs

## tl;dr

4 messages between Jun 16, 2006 and Jun 16, 2006.

replies: 3people: 3as markdown or json

Jon Smirl· Jun 16, 2006, 18:47 UTC · lore
I am running the latest parsecvs from your git tree. I am hitting a quick gpf.
oad: sible/src/html/nsHTMLLinkAccessible *....................   253 of 100111
Load: essible/src/html/nsHTMLLinkAccessib *....................   254 of 100111
Load: ble/src/html/nsHTMLSelectAccessible *....................   255 of 100111
*** glibc detected *** /home/jonsmirl/workspace/parsecvs/parsecvs:
munmap_chunk(): invalid pointer: 0x08fd1db0 ***

In the call stack I am in git_rev_list_pack line 619 doing a free. Called from parsecvs.c at 776

-- 
Jon Smirl
jonsmirl@gmail.com
Jon Smirl· Jun 16, 2006, 19:10 UTC · re: Jon Smirl · lore

Re: Running parse cvs

On 6/16/06, Jon Smirl <jonsmirl@gmail.com> wrote:
Show 10 quoted lines
> I am running the latest parsecvs from your git tree. I am hitting a quick gpf.
>
> oad: sible/src/html/nsHTMLLinkAccessible *....................   253 of 100111
> Load: essible/src/html/nsHTMLLinkAccessib *....................   254 of 100111
> Load: ble/src/html/nsHTMLSelectAccessible *....................   255 of 100111
> *** glibc detected *** /home/jonsmirl/workspace/parsecvs/parsecvs:
> munmap_chunk(): invalid pointer: 0x08fd1db0 ***
>
> In the call stack I am in git_rev_list_pack line 619 doing a free.
> Called from parsecvs.c at 776

The GPF is because git-Pack_directory is calling free(git_dir) when git_dir is an atom.

Show 5 quoted lines
>
> --
> Jon Smirl
> jonsmirl@gmail.com
>
-- 
Jon Smirl
jonsmirl@gmail.com
Linus Torvalds· Jun 16, 2006, 19:24 UTC · re: Jon Smirl · lore

Re: Running parse cvs

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

← back to recent threads