Signal unblock/defaulthandler order
@egmontkob
Submitted by Egmont Koblinger Link to original bug (#764458)
Description
Commit 171b8aae unblocks the signals and then restores their default hanlder.
Isn't it prone to race? Shouldn't it be the other way around? I.e., between the two steps the old handler is executed for pending signals which can have undesired consequences.
Would swapping their order be good? Is it the old or the new handler that's executed when a pending signal is unleashed?
Version: git master