When patching an application, it's common that you might break it and cause a segfault. It would be nice if these could be reported and handled somewhat gracefully. There is no good way to debug this sort of thing, since the code would be executing in the code cache.
If dynamorio provides any interface to inspect the origin of code in the code cache (i.e. to map an instruction back to the original binary), reporting that information would be useful. The information here suggests that generating backtraces may be complicated, but we could also attempt that.
ndrewh
commented
3 months ago
When patching an application, it's common that you might break it and cause a segfault. It would be nice if these could be reported and handled somewhat gracefully. There is no good way to debug this sort of thing, since the code would be executing in the code cache.
If dynamorio provides any interface to inspect the origin of code in the code cache (i.e. to map an instruction back to the original binary), reporting that information would be useful. The information here suggests that generating backtraces may be complicated, but we could also attempt that.