public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: git@vger•kernel.org
Cc: "Siddharth Asthana" <siddharthasthana31@gmail•com>
Subject: [BUG] replay: segmentation fault when mistyping target to --onto
Date: Thu, 11 Dec 2025 17:34:17 +0100	[thread overview]
Message-ID: <3d83161b-ec34-404a-bb0e-bf4da7ac1db5@app.fastmail.com> (raw)

    $ ./bin-wrappers/git replay --onto="$doesntexist" "$commit"'^!'
    Segmentation fault (core dumped)

I did a bisect starting on current `seen` at a0bdfe7b (Merge branch
'bc/sha1-256-interop-02' into seen, 2025-12-11). That found the “first
bad commit” 15cd4ef1 (replay: make atomic ref updates the default
behavior, 2025-11-06) (which is on `master`). I started with v2.52.0 as
the first known “good”, which I manually checked.

Same segmentation fault on `next` at 674ac2bd (Merge branch
'kh/doc-send-email-paragraph-fix' into next, 2025-12-10).

The following is basically the bisect script except I changed it to make
sense outside my own repo.

```
#!/bin/sh

make || exit 125

# Mistyped `seen` for example
doesntexist=boh1eixe
# Current commit for topic kh/doc-pre-commit-fix
commit=8cbbdc92f77a20014d9c425c8b9e4af46e492204

./bin-wrappers/git replay --onto="$doesntexist" "$commit"'^!'

if test $? = 139
then
    exit 1
else
    # Presumably regular failure:
    #     fatal: Replaying down to root commit is not supported yet!
    exit 0
fi
```

next             reply	other threads:[~2025-12-11 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 16:34 Kristoffer Haugsbakk [this message]
2025-12-11 17:56 ` [PATCH] replay: move onto NULL check before first use René Scharfe
2025-12-15 10:10   ` Phillip Wood
2025-12-15 12:04     ` Kristoffer Haugsbakk

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

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

  git send-email \
    --in-reply-to=3d83161b-ec34-404a-bb0e-bf4da7ac1db5@app.fastmail.com \
    --to=kristofferhaugsbakk@fastmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=siddharthasthana31@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox