You might find some 'coolstuff' but IDA doesnt find the xrefs and it is partially analyzed.ġ. I will take this as an example, the elf that runs in procs 6 (the one that has to do with QA flag, dongleaut, etc) Or you found that there is a new great plugin/script that makes everything easier, but you don´t want to lose your work. You might stump with someone's IDA database and you would like to continue their work.

If you want the latest version of the jump table plugin you can use this precompiled Continuing your or someone else's work in another database

compile a 'hello world' for ida, and then try to compile this. debug and release.įor that you can google, the instructions. You will see there are options for 32/64 bits. In Visual Studio, you have to correctly set the paths to where you have the sdk installed and so on. The code itself should compile correctly, but there are many options that are specific for you PC. To compile the latest plugins you will need Visual Studio and IDA sdk Many of the tools are opensource, the idc script do not have to be compiled but the plugins must be. xorloser's ps3.xml (updated lv2syscalls + sysmodules) : Ps3.xml.xorloser's PPCAltivec plugin // (reup) /.anergistic - to debug SPU code // Git - mirrors: /.Plugin tested on the eboot.bin file from the F.E.A.R.2: found and successfully created 137 jump tables.įound on hax in forum, you may wish to relocate + Added several new structures for constructing jump tables.- Fixed bug causing crash Ida Pro 6.1 ('oops! internal error 189').SPU - To be able to disassemble SPU code.3 deci3dbg - Ida Pro debugger module for Playstation 3įirst you should get all the tools you can get to make your life easier.2 Continuing your or someone else's work in another database.

Ida hexrays