Linus Torvalds writes: (Summary) I've seen code that cares about SIGFPE deeply, but it's almost
invariably about some emulated environment (eg Java VM, or CPU
emulation).
emulation).
And the siginfo data is basically never good enough for those environments anyway on its own, so they will go and look at the actual instruction that caused the fault and the register state instead, because they need *all* the information.
because they need *all* the information.
The cases that use si_code are the ones that just trapped signals in order to give a more helpful abort message.
order to give a more helpful abort message.
So I could certainly imagine that si_code is actually used by somebody who then decides to actuall act differently on it, but aside from perhaps printing out a different message, it sounds far-fetched.
emulation).
And the siginfo data is basically never good enough for those environments anyway on its own, so they will go and look at the actual instruction that caused the fault and the register state instead, because they need *all* the information.
because they need *all* the information.
The cases that use si_code are the ones that just trapped signals in order to give a more helpful abort message.
order to give a more helpful abort message.
So I could certainly imagine that si_code is actually used by somebody who then decides to actuall act differently on it, but aside from perhaps printing out a different message, it sounds far-fetched.