On windows platform, crashing with the absence of the pdbs generated a call stack WITHOUT module base address

Development Pipeline & Plugins
, ,
2

Hi,

You should use the file CrashContext.runtime-xml generated by the engine in the crash folder beside the log. The file contains a <PCallstack> element for the crashing thread. You also have all other threads callstack and there is a boolean telling if the thread crashed or not if you need to look at the other threads. As far as I’m aware, you get the module name, the base address + offset. That’s the file Epic uses to symbolicate the callstacks.

<PCallStack> LyraGame 0x00007ff6c13f0000 + 891c858 LyraGame 0x00007ff6c13f0000 + 88e8371 LyraGame 0x00007ff6c13f0000 + 88d2c0e ... LyraGame 0x00007ff6c13f0000 + ea9443e KERNEL32 0x00007ffd53bf0000 + 17374 </PCallStack>Regards,

Patrick