mirror of
https://github.com/radareorg/radare2.git
synced 2024-12-04 19:47:31 +00:00
e36ef11025
- Only 'test' opcode for x86 is currently supported (just for testing) - analysis backend generates RAnalValue's for each argument - compiles a cmp+cjmp into a RAnalCond class - de/serializes the RAnalCond into an evaluable string - Make anal api more stable * Fix a memory leak in anal_bb * Reassign anal->reg into dbg->reg - Replicate dbg->reg into dbg->anal->reg - Such nasty cascade assignation.. |
||
|---|---|---|
| .. | ||
| p | ||
| t | ||
| arg.c | ||
| debug.c | ||
| Makefile | ||
| map.c | ||
| pid.c | ||
| plugin.c | ||
| README | ||
| reg.c | ||
| TODO | ||
| trace.c | ||
Debugger API for radare2
========================
We need to connect multiple pieces...
debugger engine: vm, qemu, bochs, ptrace, mach, w32dbg...
controlflow commands: (should be splitted in two layers)
- continue -- low level
- step -- low level
- trace --- high level one
- ...
the control flow commands depend on other stuff to decide
how to work..this is for example if the arch doesnt supports
continuation, we should provide a step based continue. The
same when a watchpoint is activated and the arch didnt
supports hardware regs for this purpose.
We also need a load/store/dump/restore functions to move the
program from one engine to another (ptrace -> qemu).. we should
provide a way for all this operations between them.
[continue]
|--- check if bp api allow us to continue or we should step into..
|--- check if debug plugin supports continue
[getregs]
|--- r_reg give us a list of registers
| - dr (show bitsize debug registers) // 32 by default
| - dr 32 (show 32 bit debug registers) // depends on size
| - dr:eax (show 'eax' register value)
| - dr:al (show 8bit register 'al')
| - dr eax=33 (set 'eax' register value)