mephi42 / drtrace Goto Github PK

• Basic block is created in thread A
• Creation event is recorded into A's buffer
• Basic block is executed in thread B
• Execution event is recorded into B's buffer
• B's buffer is flushed
• A's buffer is flushed

To post-processing it appears as if basic block was executed before it was created.

Stage 0: use explicit buffer boundary comparisons
Stage 1: make use of guard page and handle faults, get rid of explicit buffer boundary comparisons

Make use of dead registers, when possible.

On fork, drtrace starts writing to the same fd from multiple processes, the resulting file is then corrupted.

Make sure drtrace works on Windows.

Make sure drtrace can run alongside other clients.
Use drmgr.