On 1/1/22 7:02 PM, Frank Heckenbach wrote:
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall
uname output: Linux mars 5.10.0-9-amd64 #1 SMP Deb
Chet Ramey wrote:
> On 1/1/22 7:02 PM, Frank Heckenbach wrote:
>
> Thanks for the report. This is a pretty good in-depth analysis of the issue.
>
> This was fixed back in March, 2021 in the devel branch as a result of
> https://savannah.gnu.org/patch/?10035 (though the fix is different from
> you
On 1/2/22 1:38 PM, Frank Heckenbach wrote:
Chet Ramey wrote:
On 1/1/22 7:02 PM, Frank Heckenbach wrote:
Thanks for the report. This is a pretty good in-depth analysis of the issue.
This was fixed back in March, 2021 in the devel branch as a result of
https://savannah.gnu.org/patch/?10035 (tho
Chet Ramey wrote:
> > After all, we're talking about silent data corruption, and now I
> > learn the bug is known for almost a year, the fix is known and still
> > hasn't been released, not even as an official patch.
>
> If you use the number of bug reports as an indication of urgency,
Why would
