Win32 resources & PDB about dnlib HOT 5 CLOSED

Cecil uses an old open sourced PDB reader written by Microsoft, but I don't think it was written by MS' PDB experts, my guess is it was written by an intern. You can debug it and see where it fails. If there are bugs in it, it's not something I'll fix.

Do you have code to reproduce this? Are you sure this only happens if you modify the Win32 resources? AFAICR, the PDB reader doesn't use anything from the Win32 resources.

You can use dnlib to loop over every type and method and print the name of the locals and sequence points (stored in instructions) and compare the output before your update and after it. dnlib has two PDB readers, one using Diagnostics Symbol Store (MS' COM PDB reader) and another managed reader written by Ki. Try both and see if they produce the same result.

from dnlib.

I should mention that I assume you let dnlib write a new PDB file after you modified the Win32 resources. If you didn't that's the first thing you should try. :)

var opts = new ModuleCreationOptions(ModuleDef.CreateModuleContext());
opts.PdbImplementation = comPdb ? PdbImplType.MicrosoftCOM : PdbImplType.Managed;
opts.TryToLoadPdbFromDisk = true;

from dnlib.

I am totally sure that it is broken when modifying Win32 resources and only with this.
However I did not try both PDB writers (dnlib is rich 😄), I'll check this.
I was asking just in case it was ringing a bell and make you answer something like "Oh yes! I know!"; Since this is not the case, I'll do some research by myself and let you know.

from dnlib.

There's only one PDB writer, but two readers because the original COM reader has limitations (can only be used in the created thread) so Ki wrote a managed reader that can be used in any thread.

When you modify the Win32 resources, do you also write a new PDB file?

from dnlib.

Yes, I write a new one. However, I don't make any change to it (I assume the magic works).

from dnlib.