Dear Ben,
I wrote:
"A double-free bug in zutils' zcat is not probable because zutils' zcat
is a C++ program that does not use neither malloc nor free."
You misquoted me as:
"this bug is impossible in C++!"
Please, don't misquote me.
On Tue, 31 Jul 2018 12:49:32 +0800 Ben Hutchings wrote:
The non-technical problem I see is that your upstream is dismissive of
valid bug reports ("but it's compatible with cat", "this bug is
impossible in C++!"), and that you are agreeing with this nonsense.
I think "valid" does not mean what you think it means.
First, 'zcat -t' is not standardized. Therefore it is not valid to
expect it to be portable.
Second, a bug report is not valid until the bad code is pointed out or
until a way to reproduce the failure is provided. Until then the bug may
be anywhere else. The problem is that in spite of my efforts I have been
unable to reproduce the problem reported in zutils' zcat. As soon as
you, or anybody else, provide a way to reproduce the problem, or point
out the cause of the bug, I'll fix it in 24h. Until then there is not
much that I can do.
Stephen Kitt, please, could you send me the smallest file (not
necessarily an initramfs) that causes zcat to crash? Thanks.
Best regards,
Antonio.
