| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2024-09-25 | Revert Break into the debugger on panic (129019) | Chris Denton | -152/+0 | |
| 2024-09-24 | Don't trap into the debugger on panics under Linux | kromych | -78/+1 | |
| This breaks `rr`, see https://github.com/rust-lang/rust/pull/129019#issuecomment-2369361278 for the discussion CC @khuey @workingjubilee | ||||
| 2024-09-22 | Reformat using the new identifier sorting from rustfmt | Michael Goulet | -1/+1 | |
| 2024-09-05 | Break into the debugger (if attached) on panics (Windows, macOS, Linux, FreeBSD) | kromych | -0/+229 | |
| The developer experience for panics is to provide the backtrace and exit the program. When running under debugger, that might be improved by breaking into the debugger once the code panics thus enabling the developer to examine the program state at the exact time when the code panicked. Let the developer catch the panic in the debugger if it is attached. If the debugger is not attached, nothing changes. Providing this feature inside the standard library facilitates better debugging experience. Validated under Windows, Linux, macOS 14.6, and FreeBSD 13.3..14.1. | ||||
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |