Heh you guys keep suprising me. This is exactly why you and nibble should start writing the big r2 book and get OReily to Publish it. As I can't seem to be able to find all the functions of r2 myself -.-'
On 20 April 2010 23:18, pancake <[email protected]> wrote: > Yo > > ----- Original message ----- >> Hey, >> >> >> I currently use Radare2 next from IDA Free and ImmunityDBG. >> I want to be (one day) be able to be pure R2. >> Anywho, thats why I post these two ideas. > > Good. Lets read > >> I know that r1 already had this. But I never figured out how to use it. >> CodeGraphing. And not just to a picture but to an OpenGL or SDL thing >> where I can scroll. > > This is already done. It was presented by nibble. Im sure he can give you > better hints about it. But basically you should do: > > af # analize code > ag > foo.dot > !xdot foo.dot > I tried this however it didnt seem to work. I figured that af is the function that says to r2, "Why I think its a great Idea for you to start analyzing the function I am currently in. (or the one @ loc x)" Then you do ag, and this writes the findings in a Graphviz kind of format on the screen. Then I called the xdot all to view the file. So I did this. and it crashed. (xdot did) I thought, why might this be. So I cat'ted the file. And I noticed the following: It did just write: digraph code { graph [bgcolor=white]; node [color=lightgray, style=filled shape=box fontname="Courier" fontsize="8"]; } Thats not enough..? I am missing quite a lot of text. So is this still work in process or is this considered to be stable? > you can use graphviz to get a png. But xdot is written in python and its > interactive, so you can easily hack to make kit do what u need. > >> >> I'd like to see the function to export the bin. Like ImmunityDBG or >> OllyDBG does I use that to Unpack packers like UPX. > > Uhm? Export the bin? You mean dump the process memory? This was done in r1 > with !dump and !restore commands. In r2 you should do it manually by getting > program maps (dm command) and printraw or printtofile that block. > > Its already done, but you should understand the commands :) its more > ortogonal. So you have to understand tools instead of actions. Like unix > philosophy aims. > This again, points out to my issue that you guys require to write a book or record your presentations. dm tells me its still TODO I'll be waiting.. ^^ >> Umm, and next from that all I'd like to see Decompiling like Boomerang >> or Hexrays does. > > There's a script in r1 to use boomerang. It works fine and can be easily > ported to r2. If you want to give a look :) > I downloaded the script indeed from r1. I see that you indeed just call Boomerang. I'll have a look if I might be able to use the script of r1 and port it to t2. >> >> Looking forward to the response. >> I guess it won't be in R2 till R2 1.0 heh > > many things can be already done without having to explicitly be implemented. > Thats why the commands are tools itself and can fit together to make what > you need. > And again that points exactly to my problem. Write a book :P hire somebody to write a book. Get your Girlfriend to do so. If I know the commands I'd be able to use my fantasy and make r2 dance my dance. (Exactly why I threw away windows, since it dances it own dance instead of mine) Well Thanks again =) Cheers, Robin > --pancake > > _______________________________________________ > radare mailing list > [email protected] > http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org > > _______________________________________________ radare mailing list [email protected] http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
