Re: git status & seg.fault

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Oct 26, 2010 at 11:45, Rado Dr. <radodr@xxxxxxxxx> wrote:
> there is output:
> Reading symbols from /usr/local/bin/git...done.
> (gdb) run
> Starting program: /usr/local/bin/git status
> [Thread debugging using libthread_db enabled]
>
> Program received signal SIGSEGV, Segmentation fault.
> hash_index_entry (istate=<value optimized out>, ce=0xb7c00c90) at name-hash.c:44
> 44 Â Â Â Â Â Â Âhash = hash_name(ce->name, ce_namelen(ce));
> (gdb) bt full
> #0 Âhash_index_entry (istate=<value optimized out>, ce=0xb7c00c90) at
> name-hash.c:44
> Â Â Â Âpos = <value optimized out>
> Â Â Â Âhash = 3198509075
> #1 Â0x080dde47 in lazy_init_name_hash (istate=0x8194180,
> name=0xbfffb34b "src/FotoPlusServer/build.xml", namelen=28, icase=0)
> Â Âat name-hash.c:59
> Â Â Â Ânr = 16273
> #2 Âindex_name_exists (istate=0x8194180, name=0xbfffb34b
> "src/FotoPlusServer/build.xml", namelen=28, icase=0) at
> name-hash.c:108
> Â Â Â Âhash = <value optimized out>
> Â Â Â Âce = <value optimized out>
> #3 Â0x080cf190 in dir_add_name (dir=<value optimized out>, base=<value
> optimized out>, baselen=<value optimized out>, check_only=0,
> Â Âsimplify=0x0) at dir.c:449
> No locals.

I haven't tried to grok all that, but you'd get a better backtrace if
you compiled git with debug flags, e.g.:

    make CFLAGS="-O0 -ggdb3"

And then did gdb ./git .... Sorry for not mentioning it to begin with.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]