Open HarukaMa opened 8 months ago
The error code, in most cases, is enough to reflect the exception type itself. More detailed information is strongly tight to QEMU target implementation and I'm afraid it's hard to retrieve in an arch agonistic way.
When a CPU exception is thrown, what we have is an error code from unicorn, however I can't find a way to directly get the exact exception (#DBG for flag TF on x86 for example). Guessing doesn't always work.
I know there are cross-arch issues, but is this even possible?