Re^3: Child process lingers after keyboard interrupt on Windows

The included code:

$SIG{'INT'} = sub { kill 'INT', $pid if $pid };

would be the Perl way to forward an interrupt. Except:

the INT signal is normally sent to all processes in the group anyway, so you only forward it like this if you know the child went to some other process group already. And then, it probably went away to avoid this kind of interrupt.
In a similar way, Windows also sends ^C (Ctrl+C) to all processes attached to that console
signals do not really exist on Windows, and there this call to kill directly kills the process, no signal sent whatsoever

Or at least this is what the documentation says. Because when I try it out, nothing works as it should since I got on Windows...

Comment on Re^3: Child process lingers after keyboard interrupt on Windows

Replies are listed 'Best First'.
Re^4: Child process lingers after keyboard interrupt on Windows by afoken (Chancellor) on Oct 23, 2018 at 21:13 UTC
The included code: `$SIG{'INT'} = sub { kill 'INT', $pid if $pid };` [download] would be the Perl way to forward an interrupt. [...] Or at least this is what the documentation says. Because when I try it out, nothing works as it should since I got on Windows... Windows has *NO* signals. Perl on Windows has a very thin emulation layer that barely works inside Perl. See also Re: Signals in Strawberry Perl: Name or number?, Re: Signals in Strawberry Perl: Name or number?, $SIG{ALRM} and windows vista?. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply] [d/l]

Replies are listed 'Best First'.

Re^4: Child process lingers after keyboard interrupt on Windows
by afoken (Chancellor) on Oct 23, 2018 at 21:13 UTC

The included code:
$SIG{'INT'} = sub { kill 'INT', $pid if $pid };
[download]
would be the Perl way to forward an interrupt. [...] Or at least this is what the documentation says. Because when I try it out, nothing works as it should since I got on Windows...

Windows has *NO* signals. Perl on Windows has a very thin emulation layer that barely works inside Perl. See also Re: Signals in Strawberry Perl: Name or number?, Re: Signals in Strawberry Perl: Name or number?, $SIG{ALRM} and windows vista?.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

[reply]
[d/l]