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

Re: parsecvs and unnamed branches

From
PRPavel Roskin <proski@gnu.org>
Date
Jun 17, 2006, 03:12 UTC
Message-ID
<1150513943.29738.15.camel@dv>
In-Reply-To
<9e4733910606162002x508ec6ccjbc36e4220ca44fd6@mail.gmail.com>
Hi, Jon!
On Fri, 2006-06-16 at 23:02 -0400, Jon Smirl wrote:
Show 7 quoted lines
> My parsecvs job died after 5 hours of CPU time. Does this tell you anything?
> 
> Pack pack-e28915a5ea09143a9139e84e24534ed888bf1c45 created
> 
> Error: branch cycle
> *** glibc detected *** parsecvs: munmap_chunk(): invalid pointer: 0x0a820198 ***
> *** glibc detected *** parsecvs: corrupted double-linked list: 0x45b1e158 ***

Obviously, memory corruption. Valgrind is likely to help, but it may take 50 hours rather than 5. It may still be worth it. Make sure to use the latest version of Valgrind and compile parsecvs without optimization with full debug information. If you can get debug info for libc, install it (on Fedora: "yum install glibc-debuginfo").

> /lib/libc.so.6(__libc_free+0x179)[0x45a554f0]
> parsecvs[0x804dec8]

You see, even some libc symbols can be found, but parsecvs is opaque. That's why debug information is useful. Make sure to keep the sources around for debugging.

-- 
Regards,
Pavel Roskin
Previous: Jon SmirlNext: Jon Smirl
Message 7 of 14 in “parsecvs and unnamed branches”
  1. Jon SmirlJun 16, 2006
  2. Keith PackardJun 16, 2006
  3. Jon SmirlJun 16, 2006
  4. Jon SmirlJun 16, 2006
  5. Keith PackardJun 16, 2006
  6. Jon SmirlJun 17, 2006
  7. Pavel RoskinJun 17, 2006
  8. Jon SmirlJun 17, 2006
  9. Pavel RoskinJun 17, 2006
  10. Jon SmirlJun 17, 2006
  11. Pavel RoskinJun 17, 2006
  12. Keith PackardJun 17, 2006
  13. Jon SmirlJun 17, 2006
  14. Keith PackardJun 17, 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.