From: Jeffrey Walton <noloader@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: bzip2-devel@sourceware.org
Subject: Re: call to ‘fprintf’ from within signal handler [CWE-479]
Date: Thu, 16 Jul 2020 11:03:53 -0400 [thread overview]
Message-ID: <CAH8yC8==ye=_cxgOraMNx-VBzGQ6YgHJiHRFwLh9D7AR2MkbOw@mail.gmail.com> (raw)
In-Reply-To: <31c7983432368f62b6d8a7c5e0f395770de3ac2e.camel@klomp.org>
On Thu, Jul 16, 2020 at 9:55 AM Mark Wielaard <mark@klomp.org> wrote:
>
> That should already have been fixed in git:
>
> commit 8ca1faa31f396d94ab927b257f3a05236c84e330
> Author: Mark Wielaard <mark@klomp.org>
> Date: Sun May 17 20:02:31 2020 +0200
Oh, sorry about that. I did not think to check master.
Jeff
prev parent reply other threads:[~2020-07-16 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 8:49 Jeffrey Walton
2020-07-16 13:55 ` Mark Wielaard
2020-07-16 15:03 ` Jeffrey Walton [this message]
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='CAH8yC8==ye=_cxgOraMNx-VBzGQ6YgHJiHRFwLh9D7AR2MkbOw@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=bzip2-devel@sourceware.org \
--cc=mark@klomp.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 read-only IMAP folder(s) and NNTP newsgroup(s).