mirror of
https://github.com/radareorg/radare2.git
synced 2024-11-26 06:30:33 +00:00
3f2677ab7f
- r2 -d gdb://<host>:<port> - register maps not yet implemented - some basic step/continue should work in cfg.debug=true - gdbwrap instance is shared between RIO and RDebug * RDebug is now arch-sensitive - Plugins describe which architectures and register sizes are supported - Native debugger is restricted to local CPU - Remote debugger (GDB) arch can be specified with -e asm.arch=arm * Fix some random warnings * Move R_ASM_ARCH into R_SYS_ARCH - Helper functions to translate id to string and string to id are now in util/sys.c (r_util) - Move all R_SYS_* from r_util to r_types - Endianness, OS, CPU and regsize is now 'global' |
||
---|---|---|
.. | ||
cxx | ||
go | ||
guile | ||
java | ||
lua | ||
perl | ||
python | ||
ruby | ||
vapi | ||
autogen.sh | ||
check-langs.sh | ||
config.mk.acr | ||
configure | ||
configure.acr | ||
do-swig.sh | ||
do-test.sh | ||
Makefile | ||
python-config-wrapper | ||
README | ||
rules.mk |
r2-swig notes ============= The valaswig integration forces us to do some changes in the r2 API. These api changes are for: - Avoid keywords in function names Every language has its own keywords, r2api should try to workaround all those keywords to avoid collisions for bindings. Example: use, del, from, continue, etc.. TODO: we need to review APIs, find better names for functions using those keywords, etc.. - Review basic data structures Linked lists, hash tables, r_db, arrays, ... must be reviewed to fit with vala and swig basics to be able to use them with simple APIs or integrate them with the syntax sugar of the target language. Example: foreach (var foo in binls.get_symbols ()) { print ("%s 0x%08"PFMT64x"\n", foo.name, foo.offset); } - Unit testing Having bindings for python, perl, ruby, .. is good for unit testing because it hardly simplifies the way to test APIs, find bugs, ... TODO: write unit testing frameworks for perl, ruby, python, etc.. - API unification for all languages All the previous development points are meant to reduce code in r2, avoid syntax exceptions, simplify api usage, and much moar ;) SWIG is not complete, there are still so many bugs to fix and so many unimplemented stuff. Here's a list of the most anoying things of it: - unsigned char * : not implemented