From: jake roggenbuck <roggenbuckjake@gmail.com>
To: git@vger.kernel.org
Subject: bug: Segfault with git diff
Date: Sat, 18 May 2024 20:02:19 -0700 [thread overview]
Message-ID: <CAEUC8gmgq_yViedLGHOeSyvR9rQK+O-8Fh9wzds=2+326ngUjw@mail.gmail.com> (raw)
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
I have found a segfault when running git diff.
> What did you do before the bug happened? (Steps to reproduce your issue)
1. After running `git diff`, git showed me that object files were empty.
2. I deleted the empty object files, and ran `git diff` again.
3. I continued deleting the empty files until `git diff` segfaulted.
> What did you expect to happen? (Expected behavior)
An error message of some type or a graceful exit.
> What happened instead? (Actual behavior)
A segmentation fault.
`Segmentation fault (core dumped)`
> What's different between what you expected and what actually happened?
Instead of closing gracefully, there was a segmentation fault.
> Anything else you want to add:
git log displays:
fatal: bad object HEAD
git branch displays:
fatal: missing object 7610511b1b4db888e8e6bb8d0ff158f932961345 for
refs/heads/main
Neither log nor branch causes the segfault.
[System Info]
git version:
git version 2.45.1
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 6.7.3-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 01 Feb 2024
10:30:35 +0000 x86_64
compiler info: gnuc: 14.1
libc info: glibc: 2.39
$SHELL (typically, interactive shell): /bin/bash
[Enabled Hooks]
Best,
Jake Roggenbuck
reply other threads:[~2024-05-19 3:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAEUC8gmgq_yViedLGHOeSyvR9rQK+O-8Fh9wzds=2+326ngUjw@mail.gmail.com' \
--to=roggenbuckjake@gmail.com \
--cc=git@vger.kernel.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.