gh-101100: Fix Sphinx warnings in library/faulthandler.rst

[hugovk]

Fix 13 warnings:

library/faulthandler.rst:11: WARNING: py:const reference target not found: SIGSEGV
library/faulthandler.rst:11: WARNING: py:const reference target not found: SIGFPE
library/faulthandler.rst:11: WARNING: py:const reference target not found: SIGABRT
library/faulthandler.rst:11: WARNING: py:const reference target not found: SIGBUS
library/faulthandler.rst:11: WARNING: py:const reference target not found: SIGILL
library/faulthandler.rst:18: WARNING: c:func reference target not found: sigaltstack
library/faulthandler.rst:73: WARNING: py:const reference target not found: SIGSEGV
library/faulthandler.rst:73: WARNING: py:const reference target not found: SIGFPE
library/faulthandler.rst:73: WARNING: py:const reference target not found: SIGABRT
library/faulthandler.rst:73: WARNING: py:const reference target not found: SIGBUS
library/faulthandler.rst:73: WARNING: py:const reference target not found: SIGILL
library/faulthandler.rst:107: WARNING: c:func reference target not found: _exit
library/faulthandler.rst:107: WARNING: c:func reference target not found: _exit

Link the SIG* py:consts to the signal module, and add ! to the c:funcs which I don't think need documenting.

• Issue: Fix all Sphinx reference warnings in the documentation #101100

---

📚 Documentation preview 📚: https://cpython-previews--118353.org.readthedocs.build/

[AlexWaygood]

PR title is interesting 👀

[hugovk]

Haha, it was a mistake, corrected now!

I had some extra stuff on main, was playing around with https://github.com/brettcannon/check-for-changed-files/ to try python/core-workflow#480 (didn't get it working...). Rebased my branch before creating the PR but it kept the old default title :)

[AlexWaygood]

Is this the same as https://docs.python.org/3/library/os.html#os._exit? Should this link to that, maybe?

[hugovk]

I don't think so, it's calling the C one from unistd.h:

cpython/Modules/faulthandler.c

Line 11 in e0ab642

# include <unistd.h> // _exit()

cpython/Modules/faulthandler.c

Lines 591 to 592 in e0ab642

	if (thread.exit)
	_exit(1);

[AlexWaygood]

I think os._exit is just a very thin wrapper around the C one:

cpython/Modules/posixmodule.c

Lines 6613 to 6619 in e0ab642

	static PyObject *
	os__exit_impl(PyObject *module, int status)
	/*[clinic end generated code: output=116e52d9c2260d54 input=5e6d57556b0c4a62]*/
	{
	_exit(status);
	return NULL; /* Make gcc -Wall happy */
	}

But yes, good point, they're not exactly the same!

[miss-islington-app]

Thanks @hugovk for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12.
🐍🍒⛏🤖

[bedevere-app]

GH-118366 is a backport of this pull request to the 3.12 branch.