diff options
| author | Jubilee <workingjubilee@gmail.com> | 2024-09-26 22:20:54 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-26 22:20:54 -0700 |
| commit | 9734723259ef8e1ae8e494f046c0773b8590a3f6 (patch) | |
| tree | 641d697af2a2056c7b522c7c74619afb47a5821d /compiler/rustc_codegen_gcc/example/alloc_example.rs | |
| parent | 0b53cecb79b57a7e76baf03b650bbe7edbd9a074 (diff) | |
| parent | d3e59a502be4f3cc2d90a252f0604985320599cc (diff) | |
| download | rust-9734723259ef8e1ae8e494f046c0773b8590a3f6.tar.gz rust-9734723259ef8e1ae8e494f046c0773b8590a3f6.zip | |
Rollup merge of #130846 - ChrisDenton:revert-break, r=Noratrieb
Revert Break into the debugger on panic (129019) This was talked about a bit at a recent libs meeting. While I think experimenting with this is worthwhile, I am nervous about this new behaviour reaching stable. We've already reverted on one tier 1 platform (Linux, https://github.com/rust-lang/rust/pull/130810) which means we have differing semantics on different tier 1 platforms. Also the fact it triggers even when `catch_unwind` is used to catch the panic means it can be very noisy in some projects. At the very least I think it could use some more discussion before being instantly stable. I think this could maybe be re-landed with an environment variable to control/override the behaviour. But that part would likely need a libs-api decision. cc ````@workingjubilee```` ````@kromych````
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/alloc_example.rs')
0 files changed, 0 insertions, 0 deletions