IDA PRO 9.1 - xml_importer.py TypeError when processing DATATYPES

[0xMirasio]

Describe the bug

when importing a ghidra XML exported database in IDA PRO 9.1 usng xml_importer.py from GhidraExtension packs, i have

Importing from: /home/user/test.xml

Processing PROGRAM                 
Processing DATATYPES               
***** Exception occurred: XML Importer failed! *****
TypeError: %d format: a real number is required, not tinfo_t

To Reproduce

take hello_word.c programs

#include <stdio.h>
#include <stdlib.h>
static int test2(int a) {
        return a& 2;
}
int main()
{
  printf("hello world");
  int x = test2(8);
  return 0;
}

compile it => import in Ghidra 11.4.2 , do a simple analysis and export it to a xml Database.
Load IDA PRO 9.1 or 9.X+ => use plugin xml_importer from ghidraExtension packs.
Select all from options

Expected behavior
Importing XML db in IDA PRO

Attachments

Environment (please complete the following information):

• os : ubuntu Noble
• Java Version: openjdk 21.0.8 2025-07-15
• Ghidra Version: 11.4.2
• Ghidra Origin: release gitub
• IDA PRO 9.1

[ryanmkurtz]

Some work has been has done for Ghidra 12.0 with regard to IDA 9.x support: #7392, #8450. You could try building the master branch to see if it works for you.

[0xMirasio]

@ryanmkurtz ah sorry didn't tell it in the issue. Yes i have used the ExtensionPack in the master branch with the laster change. It work pretty well (thansk for the work!) in both side. The solo issue is for datatypes importing from ghidra into IDA. (other side work well)

[ryanmkurtz]

Got it. Since we do not have access to IDA, we'll have to rely on the community to support this.

[skochinsky]

Hi @0xMirasio,

Could you attach a sample XML export which triggers the error and the exact script you're running in IDA so that I don't have to hunt for it?

[0xMirasio]

@skochinsky Yes of course, here is my sample.

gcc test.c -o test
=> the error will occur when importing test.xml, if you add the option 'IMPORT Datatypes' => I exported a simple test structure in the xml :

<STRUCTURE NAME="struct_test" NAMESPACE="/" SIZE="0x9">
            <MEMBER OFFSET="0x0" DATATYPE="int *" DATATYPE_NAMESPACE="/" NAME="test2" SIZE="0x8" />
            <MEMBER OFFSET="0x8" DATATYPE="byte" DATATYPE_NAMESPACE="/" NAME="test1" SIZE="0x1" />
        </STRUCTURE>

test.c

test.xml

[skochinsky]

Thanks, I could reproduce the problem! It seems the current code mixes structure IDs (expected by legacy APIs like add_struc_member) and tinfo_t objects (used by the new typeinfo APIs). I'll see if there's a way to make it work with not too many changes.