mirror of
https://github.com/radareorg/radare2.git
synced 2024-12-02 02:06:46 +00:00
7572f315ea
* meson.build: fix meson build when not on git
* meson.build: make capstone a dependency
* meson.build: make r_magic library optional
* meson.build: capstone include is already in the dependency
* meson.build: use dependencies instead of manual linking + includes
* meson.build: add travis
* flag/meson.build: include sdb dependency
* travis-script: print messages based on install system
* io/meson.build: add sdb as dependency
* syscall/meson.build: missing sdb dependency
* {parse,config}/meson.build: add sdb dependency
* travis.yml: pass INSTALL_SYSTEM var to docker
* {bin/shlr}/meson.build: add sdb_dep to r2java and bin
* install meson and ninja-build in r2-travis docker
* travis.yml: allow meson build to fail for now
* anal/meson.build: add sdb and java dependencies
* egg/meson.build: add sdb dependency
* travis.yml: meson build env should be also in the includes list
* core/meson.build: add java dep
* meson.build: use dependencies also to create main r2 dependency
* rasm2/meson.build: replace link_with with dependencies
* rasm2/meson.build: add sdb as dependency
* meson.builds: convert link_with to dependencies and fix tabs
* travis-script: change meson install prefix and set PKG_CONFIG_PATH
* travis-script: add lib64 to LD_LIBRARY_PATH
|
||
|---|---|---|
| .. | ||
| p | ||
| bp_io.c | ||
| bp_plugin.c | ||
| bp_traptrace.c | ||
| bp_watch.c | ||
| bp.c | ||
| Makefile | ||
| meson.build | ||
| 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?