RFR: 8352946: SEGV_BND signal code of SIGSEGV missing from our signal-code table

[David Holmes]

On Wed, 26 Mar 2025 14:24:55 GMT, Matthias Baesken <mbaesken at openjdk.org> wrote:

> On Linux we had recently a crash looking like this
> 
> 
> siginfo_t @ 0x00007fff2723dc98:
>   Signal: 11 (SIGSEGV)
>   Signal Code: 3 (unknown signal code)
>   Address of faulting memory reference: 0x007fff8c31629838
> 
> 
> Seems signal code 3 is
> `#define SEGV_BNDERR 3 /* failed address bound checks */`
> 
> so we should add this to our signal code table; on AIX I cannot find this code so it might be Linux-only.
> Even on Linux the define is not always available in the system headers so we better add a define .

FWIW there is also `SEGV_PKUERR`, but not sure we need to try and cater for every possibility here. Unless we are looking at the fields that will be set when these specific sub-signal occur, I'm not sure there is any real value in identifying them.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/24255#issuecomment-2756149046