mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elijah Newren <>
To: Stefano Rivera <>
Cc: Git Mailing List <>
Subject: Re: git rebase crash: merge-ort.c:2622: apply_directory_rename_modifications: Assertion `ci->dirmask == 0' failed.
Date: Tue, 20 Sep 2022 00:15:56 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


On Fri, Sep 16, 2022 at 6:24 AM Stefano Rivera <> wrote:
> Hi, I got a crash in git-rebase, a failed assertion in merge-ort.c
> $ git rebase renamed-parent
> git: merge-ort.c:2622: apply_directory_rename_modifications: Assertion `ci->dirmask == 0' failed.
> I was rebasing a branch that replaced a directory with a symlink, onto a
> branch that renamed a parent directory of the modification.
> Reproducer script attached.
> Using --strategy=recursive avoids the crash, so it's a bug in ort.
> Not subscribed, please CC me in replies.
> Thanks,
> SR
> [System Info]
> git version:
> git version 2.38.0.rc0.373.g21cbab7515
> cpu: x86_64
> built from commit: 21cbab75150d71ca294e09180c59ee529ca53957
> sizeof-long: 8
> sizeof-size_t: 8
> shell-path: /bin/sh
> uname: Linux 5.18.0-3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.14-1 (2022-07-23) x86_64
> compiler info: gnuc: 12.2
> libc info: glibc: 2.34
> $SHELL (typically, interactive shell): /bin/bash
> [Enabled Hooks]

Thanks for testing out a release candidate, typing up the detailed
report, and even finding a simple testcase!  Very cool.

I don't have a fix, but just wanted to send a note out that I've seen
your report and will take a look at it this week.

  reply	other threads:[~2022-09-20  7:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 12:42 git rebase crash: merge-ort.c:2622: apply_directory_rename_modifications: Assertion `ci->dirmask == 0' failed Stefano Rivera
2022-09-20  7:15 ` Elijah Newren [this message]
2022-10-22 19:06   ` Elijah Newren

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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

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).