ghizard

I'd like to understand the PDB situation that is causing this, but we did not provide enough details or a trace with the error. I believe that the the issue...

Sounds good. I believe that solution (1) is OBE in the master branch with a recent code push (d4861c46ac6bcb30e79da483c66b5e78fca47abc), and hopefully your issue is not seen again when that release...

Those messages might be due to limitation of SAX parser. See totalEntitySizeLimit in #1207. I’d still like your feedback of whether the PDB Universal of the next Ghidra release works...

@snowkoan Release 11.0 went out late December. It is my expectation that if you try PDB Universal in that release, you should no longer observer the error that you initially...

I believe this issue will no longer occur due to d4861c46ac6bcb30e79da483c66b5e78fca47abc which makes the issue OBE. If you have issues with the new code, please open a new ticket.

I will look into the PDB parsing to see what is going on.

There are two issues here. First is the PDB base class issue, which was worked on but not turned on due to reliable ways of portraying and saving the information......

@sweetgiorni We don't have a more official way to do this at this point, and have had recent, similar requests. We need to discuss this more internally, as there are...

We can see that the call to createFunction(program, address) can return null. And we can see where the checkInsideThunkFunction(program, address) has the issue as noted. So we can see where...

Thanks for submitting this issue. I've seen this too and worked on part of it, but it slipped my mind to change the analyzer. My plan is to just use...