radare2/libr/bp
pancake/imac 9890c6e8b0 * Fix build in OSX
- env.sh now also uses DYLD_LIBRARY_PATH
  - Fixes in ollyasm/dis to link with no global variables
    - Remove double definition of global _state
    - Same for asm_java
  - Split -shared and -Wl,-R into LDFLAGS_{LIB|LINKPATH}
    - Fixes linkage in osx
  - anal_x86_bea plugin now links correctly against BeaEgine.o
  - dietline is now #include'd from line.c
  - no debugger support yet
  - Do not externalize any variable. Some linkage does not support it
* Remove bininfo dependency .. aims to be merged into bin soon
* Added r_str_case() method to change to lower/upper case a string
2010-02-21 20:21:36 +01:00
..
p * Fix build in OSX 2010-02-21 20:21:36 +01:00
bp.c * Uppsercase classnames (rCore -> RCore) 2010-01-26 01:28:33 +01:00
handle.c * Major refactoring patch 2009-09-24 12:29:05 +02:00
io.c * Uppsercase classnames (rCore -> RCore) 2010-01-26 01:28:33 +01:00
Makefile * Add --without-pic configure flag to build radare2 2010-01-21 21:22:30 +01:00
parser.c * Major unfinished refactoring for r_debug and r_bp 2009-09-14 00:37:28 +02:00
parser.h * Major unfinished refactoring for r_debug and r_bp 2009-09-14 00:37:28 +02:00
README * Initial working implementation of software breakpoints 2010-01-21 02:38:52 +01:00
traptrace.c * Initial working implementation of software breakpoints 2010-01-21 02:38:52 +01:00

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?