Here's the results of the doodle:
I have added some comments on the given points, so you get an idea
about how the things are going to be for 0.5.
The points we have to get more attention for next release is w32, this
has been a very wanted, but never liked feature.. neither nibble or me
use windows, but I will try to change this, and do some fixes in the next
days)
About decompilation... well, we need a better code analysis engine, and
this is what we are going to focus on next release.
gdb and qemu/bochs is nothing to be ready soon, but I will prepare the
codebase to have it working on 0.6.
There are several points where I ask for volunteers. Many of them aren't
hard to implement, but some are tedious and other not prioritary, so if
you feel the need to contribute don't be shy and ask in the mailing list
or by private mail if you have any question :)
I have recently added support for signatures ('z' command)
33 decompilation -- we need better code analysis, but basic
decompilation will be in 0.5
29 bindiffing (graph) -- nibble is working on this too, pancake
has some binary diffing in C
26 better code analysis -- nibble is mainly working on this now
25 windows support -- please report bugs, pancake will
22 gdb remote support -- not prioritary atm (volunteers?) linked
to bochs/qemu
20 hardware breakpoints -- no plans for next release..will
probably be in 0.6
18 code emulation -- some work has been done in r_vm, but
needs much more refactoring
18 Debug programs in isolated environment
-- this is simple issue, any volunteer?
it's just to create a suid
program that executes a program and
setups uid, gid, chroot and
others and then execute the given
program.
14 threaded debugger -- some work will be done, but dont expect
big changes
13 radare scripting like in r1 -- please, report issues in mailing list
or privmail
13 dalvik (android) -- no plans, no hw, any volunteer? please
ask for things to be done if
you want to help on this
11 write support for RBin -- nibble will work on this, but code
analysis is prioritary atm
11 bochs and qemu support -- very low priority, this depends on gdb
support
9 pdb support -- any volunteer to convert pdb into
radare script
9 RLine with autocompletion -- no plans atm, but this feature will
come eventually
8 signature support -- DONE (we need volunteers to generate
database for packers, compilers,
function preludes, libraries, test ..)
6 web interface -- volunteers? bluszcz is probably the
only wanna-help developer for
this point. any other? :)
5 floating point debugger -- very low priority at this point
3 osx support -- x86-32 and x86-64 hardware required,
volunteers? read doc/osx fmi
3 extended dwarf support -- zero priority for next release :)
--pancake
_______________________________________________
radare mailing list
[email protected]
http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
