Therefor, its supports only Windows platform. Its pretty good and even if deci3 specification docs are leaked its saved alot of time.
It uses ProDG’s TMAPI for communication over deci3 protocol with ps3.
IDA PRO 6.1 CODE
Exceptions, Breakpoints, Step thru code.At the last time fixed some remaining bugs around half year ago, so it should be much better, but not used it much since then. Was testing it for months, catching bugs. Do not need to mention that Ida Pro 6.5 is backward compatible with 6.1, and even debugger module compiled with idasdk61 would work just fine (much better) with 6.5. So I was making this code around 6.1 version of Ida. I do own the latest build of Ida Pro, but lets be honest here, most dont. I already have experience of making gdb proxys and hosts, but not had experience of making Ida debugger modules (actually not much who did this).Okay, I hear that someone of you is asking why I did Ida module and not some kind of gdb proxy instead, and reasons are simple: It would have allowed me to use all those nice features like scripts, plugins, tracing, leaving comments in place, interface and hotkeys to which I am used to over the years.
So after some time that I spent with ProDG I realized that it just dont works for me and decided to get host debugger to communicate with Ida.
There also was a gdb client but it was pulled around 1.xx sdk (specification changed, there is no more step cmd, etc). It has some nice features (that I even miss in others debuggers) but overall… its not that good. Whoever used to debug on Playstation 3 knows that there is only one debugger available - SN Systems ProDG. Deci3dbg - Ida Pro Debugger Module for Playstation 3