blob: e5c3af6f516311cc4b1fc017c58d83b7442cbc34 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
|
tree 9e732851be2d13244e92e98aaf64127a3b0b51a1
parent 6c63506e97d6313e670e77318247bcd1f127c584
parent ae237098f8af22bd44ee3808cce97f1782eb4e18
author bors <bors@rust-lang.org> 1623262146 +0000
committer bors <bors@rust-lang.org> 1623262146 +0000
Auto merge of #1818 - landaire:feature/panic-on-unsupported-syscalls, r=RalfJung
Add support for panicking in the emulated application when unsupported functionality is encountered
This PR fixes #1807 and allows an optional flag to be specified to panic when an unsupported syscall is encountered. In essence, instead of bubbling up an error in the context of the Miri application Miri will panic within the context of the *emulated* application. This feature is desired to allow CI pipelines to determine if a Miri failure is unsupported functionality or actual UB. Please read [this comment](https://github.com/rust-lang/miri/issues/1807#issuecomment-845425076) for the rationale behind this change.
Note: this change does not cover all cases where unsupported functionality errors may be raised. If you search the repo for `throw_unsup_format!` there are many cases that I think are less likely to occur and may still be problematic for some folks.
TODO:
- [x] README documentation on this new flag
- [x] Add tests
|
