ghizard

After digging in a little further, I think the issue here is another manifestation of what I had been seeing with the Demangler, but I think yours is something specific...

@Tkain I've been working on Demangler and PDB portions of this ticket in parallel. Likely will finish/merge Demangler portion first, which will make some analysis results look worse until the...

I'd like to better understand where you are seeing these types. I first want to confirm that we are not doing something incorrectly further upstream, and I also want to...

@alandtse I'm having difficulties doing the build. I'd like to figure this out, as I had attempted and failed to use vcpkg for a different build a couple years back....

@alandtse Given your changes, I was able to successfully build the targets. I converted the PDBs to XML and can essentially confirm what you are seeing, though mine is slightly...

The pdb.xml file is created by a the Ghidra pdb.exe program on a Windows system using the msdia140.dll. In order for the program to find the dll, it must get...

Thanks for the feedback on that. I checked your branch point and also looked at history within our source files, and I'm still not sure why you get a blank...

I extended your example with ``` int __stdcall func_stdcall_1(int x, char c) { return x+1+(int)c; } int __fastcall func_fastcall_1(int x, char c) { return x+1+(int)c; } int __cdecl func_cdecl_1(int x,...

@mborgerson @GXTX There has been no progress on this other than more thoughts triggered by your query. Issue in the past was with a collision in the mangled name space....

@fenugrec The problem that you have found is different from the original problem. Your issues was fixed with 953f59317ae535cefed0949794972f8878d137b1. This fix is available starting with Ghidra 11.1. @danthespal @aerosoul94 I've...