Re: Core dump on commit

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

 



On Mon, Aug 15, 2011 at 9:30 PM, Marko Vukovic <amasniko@xxxxxxxxx> wrote:
> I get this error after running "git commit"
>
> error: Object 42504431bac2e2054483c1bbc35f1b535f8d11bb is a tag, not a commit
> Segmentation fault (core dumped)

Can you get the stack trace? Does HEAD point to
42504431bac2e2054483c1bbc35f1b535f8d11bb (iow what does "git rev-parse
HEAD" say).

> "git cat-file -p 42504431bac2e2054483c1bbc35f1b535f8d11bb" gives this:
>
> object 1b9a97613307b5c7bbc189a0e41506cb1534740a
> type commit
> tag v1.0
> tagger marko <marko@bib> Sun Aug 14 20:42:12 2011 -0400
>
> The first release

If HEAD does point to 42504431, I think you can do "git reset
1b9a976133" to reset the HEAD back to a commit object (as oppose to a
tag)

But please backup the repository somewhere, I'm still not sure how you
get into this situation. The repo may help.
--
Duy
--
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]