Re^6: Print inside SIGNALS

First snippet: <> can't be interrupted because there's no way to check <> for errors. However, the signal handler does get called once it returns.

At least on my machine (Linux), it seems to be the same buffering issue...

$ perl -wMstrict -e 'alarm 2; $SIG{ALRM}=sub{
    print "Timeout reached" };<>'
^C
$ perl -wMstrict -e 'alarm 2; $SIG{ALRM}=sub{
    print "Timeout reached\n" };<>'
Timeout reached
^C
$ perl -wMstrict -e 'alarm 2; $SIG{ALRM}=sub{
    print STDERR "Timeout reached" };<>'
Timeout reached^C
[download]

Comment on Re^6: Print inside SIGNALS Select or Download Code

Replies are listed 'Best First'.
Re^7: Print inside SIGNALS by ikegami (Patriarch) on Jul 17, 2018 at 16:18 UTC
No, "it didn't work" for you because you killed the program before the signal handler was called.	[reply]
Re^8: Print inside SIGNALS by haukex (Archbishop) on Jul 17, 2018 at 18:14 UTC
No, "it didn't work" for you because you killed the program before the signal handler was called. Have you tried the one-liners yourself? (I ran them on Ubuntu Linux, in case that makes a difference.) Are you saying you are observing different behavior than I am? If so, what is that behavior? If you're saying it's not a buffering issue, what do you think is causing the different behavior of the first two of my one-liners above?	[reply]
Re^9: Print inside SIGNALS by ikegami (Patriarch) on Jul 18, 2018 at 11:20 UTC
Let me be clear: Don't kill the program (e.g. by sending SIGINT to the program) and then complain that the rest of the program (e.g. the signal handler) doesn't run.	[reply]
Re^10: Print inside SIGNALS by haukex (Archbishop) on Jul 18, 2018 at 14:40 UTC
Re^11: Print inside SIGNALS by Veltro (Hermit) on Jul 19, 2018 at 11:05 UTC
Some notes below your chosen depth have not been shown here
Re^11: Print inside SIGNALS by ikegami (Patriarch) on Jul 20, 2018 at 18:43 UTC
Some notes below your chosen depth have not been shown here