Re: GNU Parallel Bug Reports Signal SIGCHLD received, but no signal handler set

[Rick Masters]

Ole,

Hmm, perhaps the environment that can reproduce it is more specific than I 
assumed.
The centos platform this was reproduced on is pretty old and somewhat 
customized so I'll try to find an off-the-shelf centos, perl, and/or virtualbox 
that we can both reproduce it with.
It might be a few days. 

Thank you for the response.
Rick

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Ole Tange
Sent: Tuesday, October 18, 2016 2:41 PM
To: Rick Masters <address@hidden>
Cc: address@hidden
Subject: Re: GNU Parallel Bug Reports Signal SIGCHLD received, but no signal 
handler set

On Tue, Oct 11, 2016 at 9:41 PM, Rick Masters <address@hidden> wrote:
> I believe I have isolated an issue reported here recently and 
> elsewhere and I would like to suggest a solution.

Great.

> http://lists.gnu.org/archive/html/parallel/2016-07/msg00011.html
> http://stackoverflow.com/questions/39754323/how-to-avoid-sigchld-error
> -in-bash-script-that-uses-gnu-parallel

Yes - it is an elusive bug - which is clearly there, but which has been 
impossible for me to reproduce, and thus impossible to check the fix. I need to 
have a test to see if it is fixed to avoid it coming back at a later time.

[... excellent debugging ...]

> I can reproduce this with perl 5.10.1 on centos 6.

I cannot. Can you reproduce the problem on a VirtualBox? And then give me a 
copy of that?

> Unfortunately, I'm stuck supporting the old version for years to come.
>
> It would be greatly appreciated if you could change the line in 
> question for your next version. I think changing the code to assign 
> the handler to a specific documented value not only fixes the problem, 
> but improves clarity and appears to be better supported by perl.

I will very much prefer changing the line after I can reproduce the bug.

[... code that does not reproduce the bug on Centos 6.8 from 
http://www.osboxes.org/centos/ ...]


/Ole