Extracting types.

[bukowa]

Hey is there any way to get types exported too?

[0xdea]

Hi, do you mean those types that are accessible in the GUI via View > Open subviews > Local types?

They can be easily extracted to a .h file manually via File > Produce file > Create C header file....

I don't believe idalib-rs already implements this, but if you confirm that's what you want I'll see if I can add it.

[bukowa]

Yes, exactly!

I know it's very easy to extract them manually in the IDA GUI with just two clicks. However, since I'm running an automated extraction pipeline from the terminal using your tool, having a CLI flag to automatically dump this .h file would be incredibly useful.

To give you some more context on my higher-level problem: I'm passing these extracted C-pseudo functions to an AI to build a RAG database and understand what the code does. The real trick/challenge I'm facing is mapping.
If I just give the AI a massive global .h file with all types, it loses focus. Ideally, the AI needs to know which specific types a given function actually depends on to have the right context. It's just a broader problem I'm trying to solve.

[0xdea]

Ok, thank you for the additional details. I'll look into it!

[0xdea]

I've submitted a PR to idalib-rs that implements the requested functionality. Once it's accepted, I'll add it to haruspex. Hopefully it won't take long.

[0xdea]

I believe I've solved the per-function type dump challenge! See https://github.com/idalib-rs/idalib/pull/68/changes#diff-6b32f1c65744dbc87becacd8c15073914cd6ee989b2d7048104190f2480df846.

Once the PR is merged, I'm thinking about generating a <func_name>.h header file for each decompiled <func_name>.c function that uses non-primitive types, plus a global .h file just in case.

[bukowa]

Hey thank you. I think this sounds solid and simple I can't think of better idea.