Trace memory writes in x64 processes using hardware breakpoints and disassembly.
npx skills add https://github.com/vzco/arc-probe --skill trace-writes
Please help me install this Agent Skill. Skill: trace-writes Source: https://github.com/vzco/arc-probe/tree/main/plugins/arc-probe/skills/trace-writes Command: npx skills add https://github.com/vzco/arc-probe --skill trace-writes
Find out which code writes to a specific memory address by using hardware breakpoints and live inspection, turning memory corruption mysteries into actionable insights.
Use trace-writes to monitor memory writes by setting a hardware breakpoint on the target address and then inspecting the breakpoint hits to identify the writer.
High-intent search queries and answers about installing and using this skill.
To trace memory writes, you set a hardware breakpoint on the target address to monitor access, then disassemble the instruction at the breakpoint hit to identify the writer. This maps the memory modification back to the responsible code path.
Hardware breakpoints monitor memory writes by pausing execution when a specific x64 address is accessed. They allow live inspection of breakpoint logs to isolate the exact instruction causing the memory corruption.
Yes, you can trace memory writes in multi-threaded x64 scenarios. The Skill applies hardware breakpoints and correlates breakpoint hits with function boundaries to isolate the responsible code path across concurrent threads.
The best way to identify the writer is to set a hardware watchpoint on the corrupted address, wait for the crash to trigger it, and then disassemble the instruction at the access point to map the write back to the originating code.
You map a memory write breakpoint hit back to the responsible function by inspecting the breakpoint logs and correlating the access point address with known function boundaries in the disassembly to isolate the code path.
Yes, tracing memory writes requires disassembly. After the hardware breakpoint triggers on the target address, you must disassemble the instruction at the access point to identify exactly which code performed the write.
vzcoRead and write process memory across data types via CLI, TCP, or bridge.
not-matthiasAnalyze binary code with Rizin and Radare2 to reveal functions, CFGs, and disassembly.
vzcoAnalyze binary functions to produce structured reports of disassembly, arguments, and call graphs.
yf8578Process large in-memory datasets with lazy evaluation and parallel execution.
