git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Benjamin Sergeant <bsergean@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: http git clone memory problem.
Date: Tue, 24 Jul 2007 18:45:43 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707241842270.14781@racer.site> (raw)
In-Reply-To: <1621f9fa0707241033l7ac53b97i8c8ea068be0cba2f@mail.gmail.com>

Hi,

On Tue, 24 Jul 2007, Benjamin Sergeant wrote:

> I still have the segfault with 1.5.2.4. If I try to gdb it, it abort 
> before I can do anything. Is there an environment variable that I can 
> set to disable signal handling or something in git ?

Did you gdb http-fetch?

If not, please use "sh -x git-clone..." to find out what command line to 
use.

And when you have the command line, please use valgrind to find out where 
the leak/corruption is.

There are some flags that are automatically set/unset when compiling the 
http transport, and it is not easy to know which flags are enabled in your 
setup.

But for starters, you might want to recompile http-fetch without -O2.  My 
gdb always has problems attributing the correct line, which does not 
exactly make it easier for me to debug things.  I could imagine your gdb 
is as annoying.

Ciao,
Dscho

  parent reply	other threads:[~2007-07-24 17:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24  3:44 http git clone memory problem Benjamin Sergeant
2007-07-24  9:26 ` Johannes Schindelin
2007-07-24 16:58   ` Benjamin Sergeant
2007-07-24 17:33     ` Benjamin Sergeant
2007-07-24 17:44       ` Benjamin Sergeant
2007-07-24 17:45       ` Johannes Schindelin [this message]
2007-07-24 17:53         ` Benjamin Sergeant
2007-07-24 20:13           ` Benjamin Sergeant

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=Pine.LNX.4.64.0707241842270.14781@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=bsergean@gmail.com \
    --cc=git@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).