IDB Import should consult type libraries

[emesare]

When loading an IDB/TIL we might not actually have the complete view of all types, therefore we should use a supplementary system for when a type reference would otherwise be unresolved. The most straightforward solution is to consult type libraries when the importer encounters an unresolved type reference.

https://dev-rust.binary.ninja/binaryninja/type_library/struct.TypeLibrary.html#method.get_named_type

[emesare]

More context provided by @rbran

The til file is parsed with a dependencies field, we currently ignore it, but it's basically importing those files from the ${IDA_INSTALL}/til directory. [...] I suppose the solution is to have a more complete "import idb" wizard or similar.

For now I think considering the types that are typical of being a TIL dependency would already exist within our type libraries we can go ahead with this until some better workflow exists for importing with TIL dependencies.

[rbran]

Fixed in idb-rs with: Vector35/idb-rs@84d544c
although this fix need to be expanded for similar situations, it solves this specific issue.