in reply to Re^5: trouble with custom signal handlers
in thread trouble with custom signal handlers

Just re-installing the signal handlers after the call to Safe will work with the exception of what happens while Safe is running.

I think that is the point of Safe. To make sure that *nothing* can do anything that Safe doesn't permit.

It's not trying to be polite; it is trying to impose absolute order; in order that it can provide certain guarantees.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
In the absence of evidence, opinion is indistinguishable from prejudice.
  • Comment on Re^6: trouble with custom signal handlers

Replies are listed 'Best First'.
Re^7: trouble with custom signal handlers
by Marshall (Canon) on Apr 17, 2016 at 19:19 UTC
    I think that we are "on the same page". If the interrupt is already masked out, then Safe doesn't have to do anything, but it is likely that this critter does things that it doesn't need to do. "polite" would mean not doing anything with something that was already meant to have nothing happen.

    It could very well be that there is no "safe" way to call Safe if the user programs wants to handle a signal.

[reply]

In Section Seekers of Perl Wisdom