[rt.cpan.org #102709] Unable to handle SIG interrupts

[email protected] ("Roderich Schupp via RT")
Newsgroups perl.par
Message-ID <[email protected]>
Fri Jul 17 05:25:23 2015: Request 102709 was acted upon.
Transaction: Correspondence added by RSCHUPP
       Queue: PAR-Packer
     Subject: Unable to handle SIG interrupts
   Broken in: (no value)
    Severity: (no value)
       Owner: Nobody
  Requestors: [email protected]
      Status: open
 Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=102709 >


On 2015-07-17 04:57:08, ZDM wrote:
> Really, I don't understand, why you do not want to fix this? What are
> you waiting for?

Time to think this thru. You have not convinced me yet, see below.
And it's my time and my disgression how I spend it.

> Can you give an example, when parent process under windows should exit
> on CTRL+C without waiting for a child and do not perform standard
> cleanup operations and makes zombie from the child process?

What are you talking about, there are no zombies here.

> Another thing - if I use something like this: 
>   print 'Press ENTER to continue...'; 
>   <STDIN>; 

I managed to get hold of an old laptop running Windows XP and I can't reproduce
this here: If I Ctrl-C the above example at the prompt, both the parent 
and the child get killed, so I don't see the point. 
If the script has set up a SIGINT handler, it is executed. Yeah, the cleanup
in the parent isn't run in this case, but it isn't on *nix either.
Also, there's no harm in leaving some temp files around.

> This is a typical software bug, and I watched him since using parl
> under windows. This bug is not critical, but makes software behavior
> unexpected.

Nope, _ignoring_ SIGINT is unexpected behaviour. 

Cheers, Roderich
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.