os/signal: SIGSYS documented as both handled and unhandled

[hdonnay]

Go version

go 1.22.3

Output of go env in your module/workspace:

N/A

What did you do?

Visited https://pkg.go.dev/os/signal

What did you see happen?

The documentation claims both:

A SIGQUIT, SIGILL, SIGTRAP, SIGABRT, SIGSTKFLT, SIGEMT, or SIGSYS signal causes the program to exit with a stack dump.

and

It also applies to some signals that otherwise cause no action: SIGUSR1, SIGUSR2, SIGPIPE, SIGALRM, SIGCHLD, SIGCONT, SIGURG, SIGXCPU, SIGXFSZ, SIGVTALRM, SIGWINCH, SIGIO, SIGPWR, SIGSYS, SIGINFO, SIGTHR, SIGWAITING, SIGLWP, SIGFREEZE, SIGTHAW, SIGLOST, SIGXRES, SIGJVM1, SIGJVM2, and any real time signals used on the system.

SIGSYS should be removed from whichever list is incorrect.

What did you expect to see?

SIGSYS listed as exactly one of handled or unhandled.

[mknyszek]

CC @golang/runtime

[ianlancetaylor]

Thanks for noticing. Sending a fix.

[gopherbot]

Change https://go.dev/cl/590915 mentions this issue: os/signal: remove SIGSYS from list of signals that take no action