From: Wolfgang Rohdewald <wolfgang@rohdewald.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: segfault with git rebase --abort
Date: Sun, 24 Mar 2024 23:56:28 +0100 [thread overview]
Message-ID: <7df26e3813ef76ee90c1fb02847bbb4b9bad630d.camel@rohdewald.de> (raw)
In-Reply-To: <xmqqle67pa7a.fsf@gitster.g>
Am Sonntag, dem 24.03.2024 um 14:54 -0700 schrieb Junio C Hamano:
> Wolfgang Rohdewald <wolfgang@rohdewald.de> writes:
>
> > git rebase -i
> >
> > git rebase --abort # boom
> >
> This thread _might_ be relevant.
>
> https://lore.kernel.org/git/20240218114936.1121077-1-marcel@roethke.info/
>
> The "might" is because the symptom is a sign of corruption of the
> rerere database but the discussion or the patch in there do not know
> how such a corruption happened in the first place.
>
> If you rebuild Git with Marcel's patch (there is v2 downthread, and
> we have been waiting for a v3) and it improves the situation, please
> do let us know.
Yes, the patch resolved my problem. Thanks a lot!
From the bash history below, this might be the sequence:
(git 2.39)
I think I forgot to remove one line of "<<<<<<< HEAD" before doing the first git add.
Because git rebase --abort then told me about the lockfile, the segfault probably
already happened with the second git rebase --continue.
and from then on all git rebase --abort segfaulted.
Oh - and I definitively did not mess around in .git
I do have a backup of the repo, so if you want me to look up things ...
git checkout master
git rebase -i
vi servertable.py
git add servertable.py # here I probably left that <<<< HEAD line
git rebase --continue
vi servertable.py
git add servertable.py
git rebase --continue # I think this already segfaulted
git status
df # plenty of free space
git rebase --abort
rm .git/MERGE_RR.lock
Since the patch is about rerere, I now did:
wrpc:~/tmp/kajongg (master|REBASE-i) git rerere status
src/servertable.py
wrpc:~/tmp/kajongg (master|REBASE-i) git rerere diff
error: Could not stat .git/rr-cache/a8ec6f624ee23ef2e37148a8172ebac3c6639f93/preimage: No such file or directory
fatal: unable to generate diff for '.git/rr-cache/a8ec6f624ee23ef2e37148a8172ebac3c6639f93'
wrpc:~/tmp/kajongg/.git/rr-cache (GIT_DIR!|REBASE-i) ls -lrt | tail -3
drwxr-xr-x 2 wr wr 4096 Mar 24 16:19 e6c7ce944f313fa718cad6875d4ee784c098868c
drwxr-xr-x 2 wr wr 4096 Mar 24 16:19 d0a20608fa0aafd2b234cce432ce7af567c1a94a
drwxr-xr-x 2 wr wr 4096 Mar 24 16:43 a8ec6f624ee23ef2e37148a8172ebac3c6639f93
wrpc:~/tmp/kajongg/.git/rr-cache (GIT_DIR!|REBASE-i) ls -l a8ec6f624ee23ef2e37148a8172ebac3c6639f93/
total 0
--
mit freundlichen Grüssen
Wolfgang Rohdewald
next prev parent reply other threads:[~2024-03-25 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 18:28 segfault with git rebase --abort Wolfgang Rohdewald
2024-03-24 21:54 ` Junio C Hamano
2024-03-24 22:56 ` Wolfgang Rohdewald [this message]
2024-03-25 20:46 ` Junio C Hamano
2024-04-06 20:21 ` Marcel Röthke
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7df26e3813ef76ee90c1fb02847bbb4b9bad630d.camel@rohdewald.de \
--to=wolfgang@rohdewald.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).