radare2

mirror of https://github.com/radareorg/radare2.git synced 2024-12-12 15:38:09 +00:00

History

pancake a8757a695f Fix android build and add r_core->anal_define api Fix static build (libr.a) Fix android build farm scripts Build system is still hacky		2012-09-03 01:27:52 +02:00
..
p	Fix android build and add r_core->anal_define api	2012-09-03 01:27:52 +02:00
bp.c	* More split of core/cmd.c	2012-02-27 03:07:32 +01:00
io.c	* Remove debugging printfs in the debugger	2011-07-06 01:45:45 +02:00
Makefile	Implement support for >- (pipe to editor)	2012-08-13 17:42:25 +02:00
parser.c
parser.h
plugin.c	* Use RList in r_bp	2010-06-30 01:13:09 +02:00
README
traptrace.c	* Use r_list_foreach[_safe] where appropriate.	2012-02-14 18:19:16 +01:00
watch.c

README

libr.bp
=======

Breakpoint API

- Manages list of defined breakpoints
- Determines if a stop is caused by a breakpoint
- Owns a database of multiple types of breakpoints
  - arch and os based ones
  - Supports endianness
  - r_bp_get should return a buffer and a length
- Manages conditional breakpoints expressions
- Types of breakpoints
  - software (traps)
  - conditional traps
  - hardware (registers)
  - mmu (changes page protections)
- All non-native operations are translated into evaluable expressions
  by other modules. Like changing register values and so on
  - Do we should place some callbacks for this kind of ops?
- We need to make this work also remotely
  - r_debug can handle the remoteness of the debugger backend.
  - r_io can do it also
- Watchpoints and its exception should be handled here
  - watchpoint expressions should be handled by using the r_num stuff
- Hardware breakpoints require access to registers, or pid/tid
  this is... the debugger backend. For those, the debugger backend
  should fill a callback to manage them.
  - if the debugger breakpoint handler does not manages the breakpoint
    type, r_bp must do it with r_io storing and loading bp bytes.

* Do we need the plugin API to define new breakpoints and so on?