Tracking issue for release notes of #133170: std: print a backtrace on stackoverflow

[rustbot]

This issue tracks the release notes text for #133170.

Steps

• Proposed text is drafted by PR author (or team) making the noteworthy change.
• Issue is nominated for release team review of clarity for wider audience.
• Release team includes text in release notes/blog posts.

Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [std: print a backtrace on stackoverflow](https://github.com/rust-lang/rust/pull/133170)

Tip

Use the previous releases categories to help choose which one(s) to use.
The category will be de-duplicated with all the other ones by the release team.

More than one section can be included if needed.

Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
Otherwise leave it empty.

cc @joboet, @jhpratt -- origin issue/PR authors and assignees for starting to draft text

[Mark-Simulacrum]

No need to write relnotes for something that likely won't happen.

[cuviper]

The bot knew it was fcp close -- is there ever a scenario where that would need relnotes?

[ChrisDenton]

Also discussed on Zulip.