In Dev build I have lib_burst_generated.pdb along with lib_burst_generated.dll in Plugins directory but in Release build it’s not there (it’s not in Library\PlayerDataCache\Win64\Data\Plugins\ either). I have “Copy PDB files” checked in Build Settings and there are .pdb files for other DLLs. How can I get symbols for Burst code in release build? I have Unity 2019.3.0f5, Burst 1.2.0 (not preview).
1 Like
Hey guys, any update on this? We encountering same issue
I’m not sure if it was supposed to work in the first place. Unity recommends manually searching for hash in file lib_burst_generated.txt here: Getting started with Burst – Unite Copenhagen 2019 | PPT (slide 32). Nevertheless, in Dev build the .pdb file was present and VTune was displaying correct C# source code for me, which made me hope it could work in Release mode as well.
Currently, you need to check “Development Build” to get PDBs, they are not generated otherwise (it’s not a Burst issue but the way existing PDB for assemblies are generated)
We will introduce a future version of Burst a new player settings to have Burst PDBs/debug symbols generated without having necessarily a development build.
1 Like
Hi, was this work ever done? We’re hoping to get an easier route to debugging in our playtests without building with the full development mode.
Hi,
We added a setting a while back to allow you to force debug information to be generated in builds (Force Debug Information) : This should do exactly what you are requesting.
1 Like