GNU bug report logs - #32375
Bug Gzip v1.9

Previous Next

Full log

View this message in rfc822 format

From: Johannes Przybilla <johannes.przybilla <at> rwth-aachen.de>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 32375 <at> debbugs.gnu.org, Antonio Diaz Diaz <antonio <at> gnu.org>, Bdale Garbee <bdale <at> gag.com>
Subject: bug#32375: Bug Gzip v1.9
Date: Wed, 8 Aug 2018 09:43:47 +0200

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 nested signal handler calls that update the same static object.

> Am 08.08.2018 um 06:56 schrieb Paul Eggert <eggert <at> cs.ucla.edu>:
> 
> On 08/07/2018 03:50 PM, Antonio Diaz Diaz wrote:
>> I find posix too restrictive in this respect. 
> 
> Yes, me too.
> 
> The file name length limit has been in gzip since forever, and is a
> separate issue (e.g. it happens regardless of signals). So if it is to
> be fixed it should be a separate bug number.
> 

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.