Trouble opening crash dump with debugger | Official Unity Discord | Page 1

river pier Mar 6, 2026, 10:31 PM

#

Hey guys, I'm trying to debug an annoying crash to desktop, which has generated a crash.dmp for me. I opened VS from the Unity editor so it had access to the game assets, then opened the dmp from the file menu. I get the output in the screenshot below, but I'm not sure what I need to press or do to actually figure out what went wrong. I've tried the different Debug with.. options but they shoot out error messages and won't let me attach the GameAssembly.dll to it

cold raven Mar 6, 2026, 10:34 PM

#

Is any of the stack visible if you try to do mixed/native debug?

#

Anyway the crash reason appears to be a stack overflow so if in your code that should be an easy fix

river pier Mar 6, 2026, 10:38 PM

#

cold raven Is any of the stack visible if you try to do mixed/native debug?

looks like this on native

#

#

this is mixed- I've been trying to point it to the GameAssembly.dll but it doesn't seem to want to select it

cold raven Mar 6, 2026, 10:40 PM

#

You should have or be able to open the normal debug stack trace window

river pier Mar 6, 2026, 10:41 PM

#

do you know where I can find this? I'm not very familiar with the debugger

cold raven Mar 6, 2026, 10:41 PM

#

I dont remember if it requires symbols to work but that may be why its not working with the provided "GameAssembly"

#

should be in the window > debugging though that vs version looks to be a tad old

river pier Mar 6, 2026, 10:43 PM

#

I think it's up and pointing me to this, but i still can't really see what it

#

is

cold raven Mar 6, 2026, 10:48 PM

#

You may need a new build with "copy PDB files" enabled and/or dev build

river pier Mar 6, 2026, 10:48 PM

#

argh

cold raven Mar 6, 2026, 10:49 PM

#

PDB files contain the debug symbols for windows binaries where as unix like usually embed them within the lib

#

Im not 100% if c# requires them to decode the stack but native languages do

river pier Mar 6, 2026, 10:50 PM

#

alrighty, I think I'll leave it here then

#

and maybe send over a new build with this option enabled

#

it's a very rare crash, so I have no idea what's causing it

cold raven Mar 6, 2026, 10:50 PM

#

Is this using il2cpp?

river pier Mar 6, 2026, 10:50 PM

#

yeah it is

cold raven Mar 6, 2026, 10:51 PM

#

ah then that explains it. Yea if you dont have the symbols you are shit out of luck

#

Pray you have the "backup this folder" and check for the symbol files in there

river pier Mar 6, 2026, 10:51 PM

#

I do have access to it

cold raven Mar 6, 2026, 10:51 PM

#

You may be able to rebuild this version to get them back too

river pier Mar 6, 2026, 10:51 PM

#

well, the ones on my desktop anyway

cold raven Mar 6, 2026, 10:52 PM

#

presuming you use source control

#

yea give it a go

river pier Mar 6, 2026, 10:55 PM

#

I see this

#

but it's still not turning up in the VS symbol search thingy

cold raven Mar 6, 2026, 11:03 PM

#

try copying it to be next to the dll

#

Normally when native binaries are build it will put the debug symbols in the same dir as the DLL

river pier Mar 6, 2026, 11:17 PM

#

cold raven try copying it to be next to the dll

yeah no luck

#

good idea though

cold raven Mar 6, 2026, 11:19 PM

#

I was going off what works for c++ debugging. If the dll and pdb file are there i see no reason for this to not work

#

Unless the dump is for another version and you are mistaken

river pier Mar 6, 2026, 11:21 PM

#

shouldn't be, it's just the one build that I have

#

i might go through the code again with a fine tooth comb and just see if I can spot what's causing it manually

#

thanks for your help buddy

#Trouble opening crash dump with debugger