gh-127604: Docs: Include a C stack in the faulthandler example

[ZeroIntensity]

This is to showcase the new feature in 3.14.

• Issue: Add a way of printing a C backtrace to faulthandler #127604

---

📚 Documentation preview 📚: https://cpython-previews--136081.org.readthedocs.build/en/136081/library/faulthandler.html#example

[ZeroIntensity]

@picnixz Are you around to do a quick review?

[picnixz]

I'm around for 3h max and then I'm off for 10 days.

[picnixz]

Let's omit some lines even if it won't be omitted. If we change how string_at behaves or if the way calls are performed change, then it will need us to rewrite this example. Instead, I suggest to have some ... after _Py_DumpStack

[ZeroIntensity]

I think it's ok to keep the addresses there for completeness, it's there as an example, not necessarily as a precise depiction of what happens if you call string_at(0). I was more worried about the line length or something like that.

[picnixz]

May I suggest replacing /home/python/cpython/build/lib.linux-x86_64-3.15/_ctypes.cpython-315d-x86_64-linux-gnu.so by a home that is smaller, e.g., /opt/python/lib.linux-... ?

[picnixz]

I trust you about the different line numbers (hopefully it's coming from a real example).

[ZeroIntensity]

Yeah, I just copy-pasted the output from a local run of ctypes.string_at(0).

[miss-islington-app]

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

[bedevere-app]

GH-136102 is a backport of this pull request to the 3.14 branch.