about summary refs log tree commit diff
path: root/src/tools/miri/tests/panic
AgeCommit message (Collapse)AuthorLines
2025-09-26Apply cfg(bootstrap) replacementMark Rousskov-5/+0
2025-08-24Allow `integer_to_ptr_transmutes` in testsUrgau-0/+2
2025-08-21Consolidate panicking functions in `slice/index.rs`Karl Meakin-1/+1
Consolidate all the panicking functions in `slice/index.rs` to use a single `slice_index_fail` function, similar to how it is done in `str/traits.rs`.
2025-08-07Rollup merge of #144903 - Kivooeo:panic_handler-is-not-begin, r=m-ou-seTrevor Gross-1/+1
Rename `begin_panic_handler` to `panic_handler` Part of https://github.com/rust-lang/rust/issues/116005
2025-08-06Print thread ID in panic message if thread name is unknownTrevor Gross-16/+22
`panic!` does not print any identifying information for threads that are unnamed. However, in many cases, the thread ID can be determined. This changes the panic message from something like this: thread '<unnamed>' panicked at src/main.rs:3:5: explicit panic To something like this: thread '<unnamed>' (0xff9bf) panicked at src/main.rs:3:5: explicit panic Stack overflow messages are updated as well. This change applies to both named and unnamed threads. The ID printed is the OS integer thread ID rather than the Rust thread ID, which should also be what debuggers print.
2025-08-04remove begin prefixKivooeo-1/+1
2025-07-19Give a message with a span on validation errorScott McMurray-4/+10
2025-05-19run tests on mips-unknown-linux-gnuRalf Jung-0/+2
2025-01-01Try to write the panic message with a single `write_all` callJohn Kåre Alsaker-0/+16
2024-10-10remove -Zmiri-panic-on-unsupported flagRalf Jung-16/+0
2024-10-10remove handle_unsupported_foreign_item helperRalf Jung-13/+0
2024-09-16Bump ui testOli Scherer-20/+20
2024-08-24panicking: improve hint for Miri's RUST_BACKTRACE behaviorRalf Jung-14/+14
2024-06-19Remove c_unwind from tests and fix testsGary Guo-1/+1
2024-05-27MIR validation: ensure that downcast projection is followed by field projectionRalf Jung-1/+1
2024-05-24miri: receive the blessings of validate.rsJubilee Young-1/+1
2024-05-06organize libc tests into a proper folder, and run some of them on WindowsRalf Jung-1/+1
2024-04-21the mir-validation ICE test behaves strangely on Windows hostsRalf Jung-3/+6
let's just disable it there, this code is not platform-dependent anyway
2024-04-20ensure the ICE-to-file logic does not affect our testRalf Jung-0/+1
2024-04-20re-bless testsRalf Jung-0/+2
2024-04-20Merge from rustcThe Miri Cronjob Bot-0/+12
2024-04-19make test not leak rustc crate hashRalf Jung-1/+2
2024-04-18when suggesting RUST_BACKTRACE=1, add a special note for Miri's env var ↵Ralf Jung-0/+12
isolation
2024-04-18add test checking that we do run MIR validationRalf Jung-0/+42
2024-04-17alloc_error_handler tests: directly call handle_alloc_error; test more codepathsRalf Jung-16/+26
2024-04-16implement support for __rust_alloc_error_handlerRalf Jung-0/+36
2023-07-29Change default panic handler message format.Mara Bos-15/+30
2023-05-08port tests to 2021 editionRalf Jung-3/+5
2023-04-14add test for recent unwind UB issueRalf Jung-0/+9
2023-04-10Turn off the alignment check pass, remove the panic test for itBen Kimock-11/+0
The panic test is now counted as an error test; we encounter a Terminate terminator, and emit an interpreter error, as opposed to just terminating due to a panic. So this test should have broken with https://github.com/rust-lang/rust/pull/102906 but wasn't because the Miri test suite is currently broken in rust-lang/rust: https://github.com/rust-lang/rust/issues/110102
2023-03-23A MIR transform that checks pointers are alignedBen Kimock-0/+11
2022-12-28handle unknown targets more gracefullyRalf Jung-1/+2
2022-09-21Add 'src/tools/miri/' from commit '75dd959a3a40eb5b4574f8d2e23aa6efbeb33573'Oli Scherer-0/+137
git-subtree-dir: src/tools/miri git-subtree-mainline: 3f3167fb59341ac3240ca1774f48e8c053219131 git-subtree-split: 75dd959a3a40eb5b4574f8d2e23aa6efbeb33573