git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Strasser Pablo <strasserpablo@bluewin.ch>
Cc: git@vger.kernel.org
Subject: Re: Segfault in git 1.8.1.5
Date: Sat, 09 Mar 2013 22:13:29 +0100	[thread overview]
Message-ID: <1362863609.29502.4.camel@localhost> (raw)
In-Reply-To: <2078462.OF4zRmv4ar@pablohp>

On za, 2013-03-09 at 21:16 +0100, Strasser Pablo wrote:
> Hello,
> 
> I segfault with the following command:
> 
> git checkout HEAD~1
> git branch -u origin/master
> 
> I think it's because i'm in detached head.
> A error message like cannot use this command in would be a better responce 
> than a segfault.

Confirmed.

dennis@lightning:/tmp/hacks$ gdb --args ~/code/git/git branch -u origin/master
(gdb) run
Starting program: /home/dennis/code/git/git branch -u origin/master
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
cmd_branch (argc=0, argv=0xbfffec08, prefix=0x0) at builtin/branch.c:886
886			if (!ref_exists(branch->refname))
(gdb) bt
#0  cmd_branch (argc=0, argv=0xbfffec08, prefix=0x0) at builtin/branch.c:886
#1  0x0804c26c in run_builtin (argv=0xbfffec08, argc=3, p=0x819f3f4 <commands.21695+84>) at git.c:273
#2  handle_internal_command (argc=3, argv=0xbfffec08) at git.c:435
#3  0x0804b656 in run_argv (argv=0xbfffeb74, argcp=0xbfffeb70) at git.c:481
#4  main (argc=3, argv=0xbfffec08) at git.c:556

But it's already been fixed by 8efb889: branch: segfault fixes and
validation. 
-- 
Dennis Kaarsemaker
www.kaarsemaker.net

  reply	other threads:[~2013-03-09 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09 20:16 Segfault in git 1.8.1.5 Strasser Pablo
2013-03-09 21:13 ` Dennis Kaarsemaker [this message]
2013-03-09 21:16 ` Junio C Hamano
2013-03-09 21:31   ` Strasser Pablo

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=1362863609.29502.4.camel@localhost \
    --to=dennis@kaarsemaker.net \
    --cc=git@vger.kernel.org \
    --cc=strasserpablo@bluewin.ch \
    /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).