pdb2mdb for Visual Studio 2015

README.md

The Visual Studio Tools for Unity are able to convert .NET debug symbol files (namely pdb files) to debug symbols files that are understood by Unity's scripting engine (namely .dll.mdb files) when importing both the .dll and the .pdb in the Assets folder.

If you prefer to handle the conversion yourself you need to call a tool named pdb2mdb on the .dll associated with the .pdb:

pdb2mdb MyLibrary.dll

Will produce a MyLibrary.dll.mdb usable on Unity if MyLibrary.pdb is present.

The .pdb files generated by Visual Studio 2015 can contain new informations that are not handled by the pdb2mdb file shipped by Unity.

You can download below the version that VSTU is using which handles the new 2015 format. This executable is self-contained and embeds all the references it needs, namely Mono.Cecil.

License Information:

• pdb2mdb is licensed under the Microsoft Public License (Ms-PL).
• Mono.Cecil is licensed under the MIT/X11.

pdb2mdb.exe

@yoyobbi I've tested this with Unity 5.3.4f1 and found that it works as expected (ie. stack traces contain extra debug info). This was after I failed to get any of the versions of pdb2mdb.exe that come with that version of Unity to work

I've confirmed that this works with Unity 5.2.3f1, with both Visual Studio 2015 and 2013. It would be nice if this could be distributed directly with Visual Studio Tools For Unity.

We will continue to do the PDB conversion explicitly because the automatic conversion when DLL's are imported into Unity did not work reliably for us. We have dozens of DLL's in our project, and only about half of them had their PDB files converted. Selecting both the DLL and it's PDB and reimporting explicitly did generate the MDB, but we cannot rely on this manual process.

Just tested it no unity 5.4 and it works. Strange that it is not included in the standard tools. Took me quite some time to figure out that it was the upgrade from VS2013 to VS2015 that had caused the mdb files to stop generating correctly... At least a warning message if you are on the worng version would be nice.

Thanks for the great tool. Works fine on Unity5.5.0f3.

Still works in May 2017 with VS2017 and Mono 5.0.

@jbevain I'm making a quick-n-easy GUI tool for this. Would you be able to update the official pdb2mdb NuGet package?

EDIT: The GUI tool lives at https://github.com/shravan2x/Pdb2Mdb-GUI.

For some reason, after re-installing of VS 2017, my pdb2mdb.exe disappeared from C:\ drive. My build was failing. This tool fixed my issue. Thanks!

Could you help me point to the source code from where this version of PDB2MDB was built? I am trying to build the latest version from the mono repository, but i am facing a problem with my version. However, this Executable works great. So, i just need the same version from where this was built.

Seems not to work any more. For instance:

mono pdb2mdb.exe Newtonsoft.Json.dll
Fatal error:
System.IndexOutOfRangeException: Array index is out of range.

Or is it just me?

@benclewett, that's probably because of the new portable pdb format. That binary is for the old PDB «native» format.

I got some hard time trying to get breakpoints working on Unity19.3/VS2017, this exe helped me, thx!

I confirm this works with 2017.4.40 and VS 2019

Thank you, this is terrific.

I create a new pdb2mdb, because this pdb2mdb.exe will throw exception in my case( Microsoft.Cci.Pdb.PdbDebugException: Invalid signature. (sig=1919117645) ),
if you have the same exception, you can try this:https://github.com/sczybt/pdb2mdb

I really appreciate this, thank you.

Got a System.OutOfMemoryException :(

Modern C# projects will generate a portable .pdb file which isn't compatible with pdb2mdb to generate the old full .pdb format add the following to your .csproj

<PropertyGroup Condition=" '$(Configuration)' == 'Debug' ">
  <DebugType>Full</DebugType>
</PropertyGroup>