From: Pavel Roskin <proski@gnu.org>
To: Bill Yoder <byoder@cs.utexas.edu>
Cc: git@vger.kernel.org, Wolfgang Denk <wd@denx.de>
Subject: Re: 1.3.2 git-clone segfaults
Date: Wed, 17 May 2006 15:29:25 -0400 [thread overview]
Message-ID: <1147894165.16654.10.camel@dv> (raw)
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
next prev parent reply other threads:[~2006-05-17 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 18:32 1.3.2 git-clone segfaults Bill Yoder
2006-05-17 18:41 ` Fernando J. Pereda
2006-05-17 18:46 ` Junio C Hamano
2006-05-17 19:27 ` Bill Yoder
2006-05-17 19:29 ` Pavel Roskin [this message]
2006-05-17 23:52 ` Pavel Roskin
2006-05-18 0:54 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1147894165.16654.10.camel@dv \
--to=proski@gnu.org \
--cc=byoder@cs.utexas.edu \
--cc=git@vger.kernel.org \
--cc=wd@denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox