git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: Emily Klassen <forivall@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git log --graph --no-graph can cause segfault
Date: Sat, 8 Feb 2025 11:44:59 +0700	[thread overview]
Message-ID: <Z6bhS7THkV2ovXfQ@danh.dev> (raw)
In-Reply-To: <CADY4h_qagYhSP2kz=zNSjfskN1ODxLf1DjEME6BdYw6j-JEAhA@mail.gmail.com>

On 2025-02-07 19:34:11-0800, Emily Klassen <forivall@gmail.com> wrote:
> > What did you do before the bug happened? (Steps to reproduce your issue)
> 
> $ git config --get alias.l
> log --pretty=oneline --abbrev-commit --decorate --graph
> 
> $ git --no-pager l --reverse --no-graph --name-status
> e83c516331 Initial revision of "git", the information manager from hell
> error: git died of signal 11
> 
> > What did you expect to happen? (Expected behavior)
> 
> I expect the commit listing to display successfully.
> 
> > What happened instead? (Actual behavior)
> 
> Git seems to have crashed. My best guess is that some state gets set with the
> first `--graph` flag which is not cleared with the `--no-graph` flag.
> 
> > What's different between what you expected and what actually happened?
> 
> Git crashed.

Given commands yields: "fatal: Out of memory, realloc failed" in my
system. But it's fixed by jk/combine-diff-cleanup, which is merged
into master.

Would you try to run from master branch to see if your problem has
been fixed?

-- 
Danh

  reply	other threads:[~2025-02-08  4:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-08  3:34 git log --graph --no-graph can cause segfault Emily Klassen
2025-02-08  4:44 ` Đoàn Trần Công Danh [this message]
2025-02-08  5:51   ` Emily Klassen

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=Z6bhS7THkV2ovXfQ@danh.dev \
    --to=congdanhqx@gmail.com \
    --cc=forivall@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 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 NNTP newsgroup(s).