All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian <crich-ml@beronet.com>
To: Julian Phillips <julian@quantumfyre.co.uk>
Cc: git@vger.kernel.org
Subject: Re: git died
Date: Thu, 26 Apr 2007 14:20:52 +0200	[thread overview]
Message-ID: <46309924.70401@beronet.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704261126300.15751@reaper.quantumfyre.co.uk>

Julian Phillips wrote:
> On Thu, 26 Apr 2007, Christian wrote:
>
>> hi list,
>>
>> i've got git-1.5.1 here and did a git push to a http based 
>> repository, i got a segfault :(
>>
>> please see the logs :
>
> ...
>
>> root@beroTester:/usr/src/mISDN# gdb git core
>> GNU gdb 6.0
>> Copyright 2003 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 "i386-linux"...
>>
>> warning: core file may not match specified executable file.
>> Core was generated by `/usr//bin/git-http-push
>
> git-http-push is a separate program.  You might want to try "gdb 
> git-http-push core"?
>
Loaded symbols for /lib/tls/libnss_dns.so.2
#0  decode_tree_entry (desc=0xbff5110c, buf=0x0, size=454) at tree-walk.c:10
10              while ((c = *str++) != ' ') {
(gdb) bt
#0  decode_tree_entry (desc=0xbff5110c, buf=0x0, size=454) at tree-walk.c:10
#1  0x0804b9a8 in mark_tree_uninteresting (tree=0x80d0240) at revision.c:65
#2  0x080534cd in main (argc=2, argv=Cannot access memory at address 0x1ca
) at http-push.c:1998
(gdb)

  reply	other threads:[~2007-04-26 12:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26  9:52 git died Christian
2007-04-26 10:28 ` Julian Phillips
2007-04-26 12:20   ` Christian [this message]
2007-04-26 19:51     ` Linus Torvalds
2007-04-26 20:55       ` Junio C Hamano

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=46309924.70401@beronet.com \
    --to=crich-ml@beronet.com \
    --cc=git@vger.kernel.org \
    --cc=julian@quantumfyre.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.