DynamoRIO / DynamoRIO/dynamorio
Treat OP_monitor address as a memory reference in the IR?
Open
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 629
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
Today DR's IR considers the address in eax/rax for OP_monitor to just be a register source and not a memory reference. Perhaps it should be considered a memref even if there would be no fault on a bad address (and thus all tools like Dr. Memory would be forced to special-case it just like prefetch instructions)? The memory size would be read from cpuid, though that just gives a min and max monitor-line size.
Contributor guide
Assessment
This issue has not been assessed yet.