Re: git describe --tags --long barfs on new tags?

From: Mikael Magnusson <mikachu@gmail.com>
Date: Jul 2, 2008, 19:56 UTC
Message-ID: <237967ef0807021256j3e67bceaoecbb8f37112db2ab@mail.gmail.com>
In-Reply-To: <20080702154506.7b83bae8@crow>

2008/7/2 Mark Burton <markb@ordern.com>:

Show 16 quoted lines

>
> Howdy folks,
>
> Discovered this today:
>
> ~/git[master]$ git tag mb
> ~/git[master]$ git describe
> v1.5.6.1-156-ge903b40
> ~/git[master]$ git describe --tags
> mb
> ~/git[master]$ git describe --tags --long
> Segmentation fault (core dumped)
>
> Hope this is useful info.
>
> BTW - just started using git and I am very impressed with it - took me a while to get my head around the "index" but now I wonder what the problem was.

Here's a backtrace, i tried to follow the code but got confused and gave up.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa7cd26c0 (LWP 9670)]
0x080615f2 in describe (arg=0x80e4e9e "HEAD", last_one=1) at
builtin-describe.c:207
207				show_suffix(0, n->tag->tagged->sha1);
(gdb) bt
#0  0x080615f2 in describe (arg=0x80e4e9e "HEAD", last_one=1) at
builtin-describe.c:207
#1  0x08061bd8 in cmd_describe (argc=0, argv=0xafcd25f4, prefix=0x0)
at builtin-describe.c:360
#2  0x0804b1bf in handle_internal_command (argc=3, argv=0xafcd25f4) at git.c:252
#3  0x0804b888 in main (argc=3, argv=0x41c294c0) at git.c:463
(gdb) print n
$1 = <value optimized out>
(gdb) print cmit
$3 = (struct commit *) 0x81476a8
(gdb) print cmit->util
$4 = (void *) 0x8147430
(gdb) print *(struct commit_name*)cmit->util
$5 = {tag = 0x0, prio = 1, sha1 =
"\tEt\"±d6ª\033\005\230\237\035ëR\226¼á\017\230",
  path = 0x814744c "mb"}

-- 
Mikael Magnusson