When packaged game crashes, Saved/Logs file doesn't contain debug info

Development Programming & Scripting C++
1

Hey everyone, I have a packaged game (Development build) that occasionally crashes. I remember in the past, the log always contained debug information, such as the function names and the code line where the crash happened. I pasted below what it looks like now, notice the entire callstack just showing UnknownFunction. My guesses are that some default setting may have changed between UE engine versions or that we have accidentally changed a setting. I have spent some time already fruitlessly trying to get debug information to show up in built games again. Does anyone know how to enable debug information in builds?

We have checked the packaging setting Project - Packaging - Include Debug Files, but this hasn’t fixed the issue. Also, we’re making builds with a source built engine using RunUAT with the command listed below. I’m not sure if the Include Debug Files settings affects a build started with the command. Any help or insights are appreciated!



"C:/UnrealEngine/Engine/Build/BatchFiles/RunUAT" BuildCookRun -project="C;/Projects/MyGame/MyGame.uproject" -noP4 -platform=Win64 -clientconfig=Development -cook -build -stage





[2018.02.07-03.43.39:586][438]LogWindows: Warning: URL: ../../../Engine/Binaries/Win64/CrashReportClient.exe "C:/Program Files (x86)/Steam/steamapps/common/MyGame/MyGameV2/Saved/Crashes/UE4CC-Windows-F7D187924898A173A794A09CB2814C09_0001" -AppName=UE4-MyGameV2 -CrashGUID=UE4CC-Windows-F7D187924898A173A794A09CB2814C09_0001 -DebugSymbols=..\..\..\Engine\Intermediate\Symbols
[2018.02.07-03.43.39:586][438]LogWindows: Could not start CrashReportClient.exe
[2018.02.07-03.43.39:586][438]LogMemory: Platform Memory Stats for WindowsNoEditor
[2018.02.07-03.43.39:586][438]LogMemory: Process Physical Memory: 1178.25 MB used, 1410.89 MB peak
[2018.02.07-03.43.39:586][438]LogMemory: Process Virtual Memory: 3061.05 MB used, 3086.07 MB peak
[2018.02.07-03.43.39:586][438]LogMemory: Physical Memory: 8088.15 MB used,  8251.01 MB free, 16339.16 MB total
[2018.02.07-03.43.39:586][438]LogMemory: Virtual Memory: 3498.36 MB used,  8251.01 MB free, 8388608.00 MB total
[2018.02.07-03.43.39:586][438]LogWindows: Error: === Critical error: ===
[2018.02.07-03.43.39:586][438]LogWindows: Error:
[2018.02.07-03.43.39:586][438]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000168
[2018.02.07-03.43.39:586][438]LogWindows: Error:
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x000000003FF89E4D MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x000000003FF89037 MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x000000004201A50A MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x0000000041FEA9EF MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x0000000042C7F6B6 MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x0000000042C82FD8 MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x0000000040126F36 MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x00000000401271D0 MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x0000000042C94C1F MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x0000000042C98E08 MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x00000000426CF09F MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x00000000426D569F MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x000000004250DC40 MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x000000003FF0A6E8 MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x000000003FF1994F MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x000000003FF199BA MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x000000003FF26B78 MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x0000000043E1B5FB MyGameV2.exe!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x0000000076F459CD kernel32.dll!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x000000007707A2E1 ntdll.dll!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error: [Callstack] 0x000000007707A2E1 ntdll.dll!UnknownFunction ]
[2018.02.07-03.43.39:586][438]LogWindows: Error:
2

Can someone tell me what the default behavior should be when you make a Development build and the game crashes? Is it to be expected that the call stack doesn’t show the function names?

3

This may help:Are you sure that the executables match the pdbs? Can you give me more details about your build setup?

You can try something like this: Run the game on a designer’s machine, type in the console ‘debug crash’. A new crash will be saved in : C:\Users[user]\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppCrash_UE4-[gamename]. Copy and open the .dmp file in the visual studio. Get the executable and the pdbs from the build. ‘Set symbol paths’ and debug the minidump.

If your pdbs and executables are ok, you will get the correct callstack.

Taken from: