From: "Jan-Otto Kröpke" <mail@jkroepke.de>
To: git@vger.kernel.org
Subject: git tag -l --format results into a malloc fatal error, if tag is signed.
Date: Tue, 22 Nov 2022 09:01:16 +0100 [thread overview]
Message-ID: <CAAsn9Yxbb3-4iTfD8gf_EhVbE+yKJdT=Vb5ojeFZOHvMutUn2Q@mail.gmail.com> (raw)
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
Create a signed git tag signed by a SSH key and run this command
(orginally executed by goreleaser).
% git -c log.showSignature=false tag -l --format='%(contents:body)' v4.2.2
What did you expect to happen? (Expected behavior)
Command executed successfully
What happened instead? (Actual behavior)
% git -c log.showSignature=false tag -l --format='%(contents:body)' v4.2.2
fatal: Out of memory, malloc failed (tried to allocate
18446744073709551323 bytes)
What's different between what you expected and what actually happened?
See above
Anything else you want to add:
Reference repository: https://github.com/jkroepke/helm-secrets
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.38.1
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Darwin 22.1.0 Darwin Kernel Version 22.1.0: Sun Oct 9 20:14:54
PDT 2022; root:xnu-8792.41.9~2/RELEASE_X86_64 x86_64
compiler info: clang: 14.0.0 (clang-1400.0.29.102)
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/zsh
[Enabled Hooks]
next reply other threads:[~2022-11-22 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 8:01 Jan-Otto Kröpke [this message]
2022-11-22 17:48 ` git tag -l --format results into a malloc fatal error, if tag is signed René Scharfe
2022-11-23 0:20 ` Junio C Hamano
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='CAAsn9Yxbb3-4iTfD8gf_EhVbE+yKJdT=Vb5ojeFZOHvMutUn2Q@mail.gmail.com' \
--to=mail@jkroepke.de \
--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.
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).