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

Re: 1.3.2 git-clone segfaults

From
PRPavel Roskin <proski@gnu.org>
Date
May 17, 2006, 19:29 UTC
Message-ID
<1147894165.16654.10.camel@dv>
In-Reply-To
<879BAFDD-87DB-4041-8753-5D63630076B5@cs.utexas.edu>
On Wed, 2006-05-17 at 13:32 -0500, Bill Yoder wrote:
> /usr/local/downloads/git-1.3.2/git-clone: line 323: 25972  
> Segmentation fault      git-http-fetch -v -a -w "$tname" "$name" "$1/"

I've seen git-http-fetch segfaults many times when cloning qgit, but it's hard to reproduce on demand.

I think you should compile git without optimizations and allow coredumps (ulimit -c unlimited), then load git-http-fetch in gdb with the core (gdb --core=core git-http-fetch) and run bt to see the backtrace.

-- 
Regards,
Pavel Roskin
Previous: Bill YoderNext: Pavel Roskin
Message 5 of 7 in “1.3.2 git-clone segfaults”
  1. Bill YoderMay 17, 2006
  2. Fernando J. PeredaMay 17, 2006
  3. Junio C HamanoMay 17, 2006
  4. Bill YoderMay 17, 2006
  5. Pavel RoskinMay 17, 2006
  6. Pavel RoskinMay 17, 2006
  7. Linus TorvaldsMay 18, 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.