Hello.
We believe to have found a bug in gzip's signal handler.
Attached will you find our bug report.
Excited to hear from you!
Greetings from Germany,
Johannes Przybilla
Gzip v1.9
In `gzip.c`, the signal handler `abort_gzip_signal` calls the function `remove_output_file` in a signal co
I agree that the POSIX standard is quite restrictive in this respect.
However I believe that is for a good reason.
Performing non-atomic memory operations on static objects in a signal handler
can cause problems with reentrancy.
This can lead to undefined behaviour for example in the case of neste
;ofname'
instead of 'remove_ofname‘.
Therefore the non-volatile access still occurs in the signal handler.
Could you look into that?
Best regards,
Johannes
> Am 08.08.2018 um 11:34 schrieb Paul Eggert :
>
> Johannes Przybilla wrote:
>> This can lead to undefined behaviou
