| Summary: | vex x86->IR: unhandled instruction bytes: 0xF 0x3F 0x7 0xB | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Christian <christian.friis> |
| Component: | memcheck | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 3.12.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Christian
2019-09-25 20:16:23 UTC
0F 3F seems to me to be undefined, and 0F 0B is the normal UD2. So as far as I can see, V is behaving correctly. Given that your program continues to run, I'd guess it catches the SIGILLs and continues. It might be quieter if you give the --sigill-diagnostics=no flag. |