dev747368

I think support for swift binaries was added fairly recently to Ghidra, so this data type size mismatch may be a new issue for those binaries vs. the same binary...

If you are okay with re-importing the binary, you can just change the "Language" field before clicking ok. It should pop up a table of arch/compiler combos (and there is...

The "non recommended" was a reference to the ability to choose an arbitrary cpu arch/compiler during import, even if its incorrect. As far as recommended ways of reusing type info...

I'm only seeing 2 cspec's that have integer_size=8: swift and golang (on 64 bit archs). Everything else is 4 bytes, except for the obvious 16 bit platform cspecs that have...

> Is Ghidra then wrong for inferring that `int` is 8 bytes long? If this binary was indeed compiled with a compiler in which `int` is 8 bytes, why is...

Sorry about late response, but as far as I can tell, this issue is a known issue with our current ability of translating dwarf local variable information into ghidra local...

I'm not 100% certain I'm following your description of the issue. Are you using the Import dialog, or the Batch import dialog? When you talk about adding another option to...

So, if the options in the Batch import dialog were saved and restored during the next usage of the Batch import, it would improve your workflow?

If the .pdb that you are worried about is the projectg.pdb that you shared earlier, when I import it it adds hundreds of data types to the data type tree....

Could you check your application logs and see if there are any errors when just opening it once the first time?