-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PDB0009 Invalid type name #109
Comments
What version of the compiler is this compiled with? |
(you can ignore the error, btw) |
The PDB and DLL? I don't know if I can find out since I didn't build them. Is that information embedded in one of the files? The csproj from the sources contains ProductVersion <PropertyGroup Condition=" '$(VisualStudioVersion)' != '' And $(VisualStudioVersion) > 10.0 ">
<LangVersion>4</LangVersion>
</PropertyGroup> But only a lower bound could be inferred from that, I guess.
👍 Is there a way I could have figured this out by looking at docs? |
If these binaries were built by an old compiler (pre-Roslyn, that is before VS 2015) it is possible that some of the metadata and debug information is bad. The old compiler had a bunch of bugs. I can take a look if you can share the binary and the PDB with me. |
Re errors: Most of the conversion errors are recoverable. If the converter produces PDB then you're good. The converter skips bad data and continues converting. |
If you have time and want to look, let me know where you want me to send it. If you're confident that I'm not losing anything important, don't let me waste your time. 😃 |
My basic goal is to achieve source-stepping while incurring as little coupling as possible to Microsoft PDB format details at a certain point in time. If this conversion is not lossy in any way which could affect source stepping and debug evaluation, maybe I'll stick with this over Windows PDB rewriting. seealso |
Ran into a couple of these, too:
|
When converting Windows PDBs to portable PDBs, I'm getting this diagnostic:
How should I address this issue?
The text was updated successfully, but these errors were encountered: