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

On 7/24/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 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

I got that, but it's not super-usefull ... I will try valgrind instead.

[bsergean@marge1 sandbox]$ gdb /home/bsergean/git/bin/git-clone
/tmp/corefiles/core.18531
GNU gdb 6.6-1mdv2007.1 (Mandriva Linux release 2007.1)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-mandriva-linux-gnu"...
"/home/bsergean/git/bin/git-clone": not in executable format: File
format not recognized
(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
Core was generated by `git-http-fetch -v -a -w remotes/origin/html
cc13f556fc72f6f0670e61599363f6e3277'.
Program terminated with signal 6, Aborted.
#0  0xbfffe410 in __kernel_vsyscall ()
(gdb) where
#0  0xbfffe410 in __kernel_vsyscall ()
#1  0xb7c78590 in ?? ()
#2  0xb7d7aff4 in ?? ()
#3  0xb7bd7aa0 in ?? ()
#4  0xbf928f84 in ?? ()
#5  0xb7c79e21 in ?? ()
#6  0x00000006 in ?? ()
#7  0xbf928ef8 in ?? ()
#8  0x00000000 in ?? ()





>
>

  reply	other threads:[~2007-07-24 17:53 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
2007-07-24 17:53         ` Benjamin Sergeant [this message]
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=1621f9fa0707241053i23f0e3d4v4a1d50f5a4c5f9e6@mail.gmail.com \
    --to=bsergean@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --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).