|
From: | GNU bug Tracking System |
Subject: | [debbugs-tracker] bug#13535: closed (timeout command not working when SIGALRM blocked) |
Date: | Fri, 25 Jan 2013 03:13:02 +0000 |
Your message dated Fri, 25 Jan 2013 03:12:24 +0000 with message-id <address@hidden> and subject line Re: bug#13535: timeout command not working when SIGALRM blocked has caused the debbugs.gnu.org bug report #13535, regarding timeout command not working when SIGALRM blocked to be marked as done. (If you believe you have received this mail in error, please contact address@hidden) -- 13535: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13535 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: timeout command not working when SIGALRM blocked Date: Wed, 23 Jan 2013 18:44:49 +0100 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 Hi there, If the calling process has SIGALRM blocked, timeout simply never times out. Find attached a small program to demonstrate the problem and a patch to fix it by unblocking the necessary signal (at least on x86/linux). If this is intended behavior, I would suggest to document it explicitly to prevent people from tapping into the same pitfall that I hit. Greetings Stephanblocksigalrm.pl
Description: Perl programunblock_sigalrm.patch
Description: Text Datasignature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Subject: Re: bug#13535: timeout command not working when SIGALRM blocked Date: Fri, 25 Jan 2013 03:12:24 +0000 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 On 01/23/2013 05:44 PM, Stephan Krempel wrote:Hi there, If the calling process has SIGALRM blocked, timeout simply never times out. Find attached a small program to demonstrate the problem and a patch to fix it by unblocking the necessary signal (at least on x86/linux).The sigprocmask gnulib module is used if the sigaction module is needed, so we should be able to use sigprocmask unconditionally here. There is even an implementation for windows included if needed.If this is intended behavior, I would suggest to document it explicitly to prevent people from tapping into the same pitfall that I hit.I agree with your patch, and have attached an updated version. Hmm I suppose we should also do this for SIGCHLD as a follow on from: http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=73d46261 thanks, Pádraig.timeout-block-alrm.patch
Description: Text Data
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |