mirror of
https://github.com/radareorg/radare2.git
synced 2025-03-06 13:29:46 +00:00
d9e77ca0d1
* use set_trace_bit and clear_trace_bit macros * use PT_ATTACHEXC since PT_ATTACH will be deprecated in the future and we are interested in receiving mach exceptions * first attempt to handle mach exceptions * api change: added a parameter to r_core_setup_debugger at least in OS X this function was producing double attachment. I've added a boolean value to indicate when use dpa. * added pipe to communicate between main process and traced process by far this is not a good implementation. We should develop a better approach/design to save all the exceptions and handle them accordingly. This is the initial implementation * bring back ptrace for stability and in order to merge this into master
RIO design
==========
rio api allows to seamlessly access to underlying IO backends
and define rules on top of it to act as an mmu.
What do io.va means?
--------------------
- obey sections
- Plugins
Actions
-------
- open
- read
- seek
- write
- close
Layers
------
- cache caches write ops and modifies reads
- map allows to map a certain file at a given offset
- sections like maps, but provide more information for virtual addressing
Features
--------
- undo
- buffer
- desc
fn read(io: IO) {
ut64 offset;
if io.offset
}