rev_brain Homepage

What is rev_brain?

rev_brain is a tool to help the reverse engineer and the programmer alike in the art of reverse engineering.

Could you please explain it better?

Of course. rev_brain is fed with the output of a disassembler, and then analyzes it. There are very nice disassemblers all around (bastard, dasm, IDA...) and I didn't want to write another one.

At the moment rev_brain just works with IDA .lst files, but I'm coding for bastard support (I like bastard because it's OPEN SOURCE, IDA is not).

rev_brain collects information from the disassembled output, and then there is an engine which processes them. If you want more, read the README.tech file which comes in the distribution.

Pre-Alpha status
 v.0.0.1c
  - function and arguments parsing

 v.0.0.1d <------------- WE ARE HERE NOW (it's 6th Oct 2001)
  - basic analysis of function (calls and args)
  - dumping output in a file

 v.0.0.1e
  - basic register propagation algorithm
  - WIFE recognition (WhileIfForElse ;)

Let's go to Alpha status =)
Alpha status
 v.0.0.2
  - make use of ./configure
  - split analizer.c looking forward to plug-ins
  - program complexity analizer
  - WIFE analysis and interpretation
 v.0.0.2a (this will last a while)
  - program dumping in an intermediate language
 v.0.0.2b
  - IDA file checker more paranoic
 v.0.0.3
  - program dumping in C language (hitting 50% of file at least)
 v.0.0.3a
  - write plugin support

Once the program dumps in C we can point to Beta!
Beta status
 v.0.0.4
  - major program rewriting and tidyups
  - adding more options (interactivity)
 v.0.0.5
  - adding bastard support
 v.0.0.6
  - adding dasm support
 v.0.0.7
  - adding file automatic recognition
 v.0.0.8
  - make program complexity analizer finer
 v.0.1.0
  - multithreaded fashion
 v.0.1.1
  - looking for a nice GUI

I'm studying:

flex, for a better integration with regular expressions
the gcc v.3 manual, for a better work in decompilation
posix threads user guide, to use threads in rev_brain
Cristina Cifuentes documents, for a scientific analysis of decompilation

I'm reverse engineering:

cscope, for flex integration and general data structure handling
bastard, to see if integration with this package is possible
grep, to see if it's possible to implement it with memory mapped files

I'm reading:

Linux Device Drivers 2nd edition, for fun =)

rev_brain decompiler homepage

What is rev_brain?

Could you please explain it better?

Which disassemblers are currently supported?

How does rev_brain work?

What's rev_brain horizon?

What is the author doing at the moment for rev_brain?

Best viewed at 80x25