22 May
2018
22 May
'18
10:48 a.m.
Hi Sylvain,
So, you are the author of the README and the web page, who did all the work
with Calypso.:)
I feel more comfortable working with C/C++ than Python.
The patch you couldn't publish 'cause of Hex-Rays copyrights.
In the case of the hook, in what file should it be placed?
Calling convention?
In C++ it should create the same IDA structs as in Python.
Where can I find their description?
I'm using IDA + SDK 6.6.
Thank you,
Nikos
On Tue, May 22, 2018 at 8:17 AM, Sylvain Munaut <246tnt(a)gmail.com> wrote:
Hi,
According to target_dsp/ida/README.txt, which is
not signed, some of the
modifications to the Hex-Rays IDA SDK need the
author's help. I have compiled the processor with most of its attributes,
but I could use help with the stub feature to load include files.
I don't have the patch any more, I wrote it for IDA 5.5 and most of it
actually got merged by hexrays into mainline for 6.0, but not the type
system.
I actually didn't write support for it really ... just added a hook
that did nothing and that allowed to load the .h once and then the
patch wasn't needed.
I did a post in the hex-rays forum asking how the type system worked,
search
for it, and I just implemented the hooks with default return values.
The other option (which might be easier given it's really simple
struct) is to convert the .h with a python script to IDC/IDAPython
commands to
create the 'struct' in IDA.
Cheers,
Sylvain