mirror of
https://github.com/radareorg/radare2.git
synced 2024-12-05 20:17:43 +00:00
fcbcc00d1e
- Integrated with core 'as' command. as? for help - Display formatted parametters of syscalls - Needs to fully implement this everywhere - Syscall argument parsing is not yet complete (<4args) - r_debug_arg_{set|get} * Implement continue until syscall on Linux debugger backend * Lot of syntax cleanup to use the new code convention - Clean r_sign, r_search, r_syscall * Define global R_SYS_ARCH, _OS and _BITS - Handle asm.os and asm.arch to hook r_syscall plugins - Display 8 or 16 zeros depending on asm.bits - Added r_str_filter () to filter nonprintable chars --HG-- rename : libr/search/stripstr.c => libr/search/strings.c |
||
---|---|---|
.. | ||
p | ||
t | ||
arg.c | ||
debug.c | ||
handle.c | ||
Makefile | ||
map.c | ||
pid.c | ||
README | ||
reg.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)