Crash report missing of debugger
See original GitHub issueDescribe the bug Related to #2532 . The results of the debugger are not appended to the logs of the game. That way we have no additional information on what caused the crash.
To Reproduce
While in game, turn on this game option:
Then enable free camera (CTRL + V by default) and orientate your camera like in this screenshot:
Make sure the commander is selected. Then hover your mouse across the sky and interact with UI elements (by clicking on them) that are rendered over the sky. This reliably produces a hard crash. The details about the crash are missing:
debug: [uiutil.lua, function UIFile()] - Unable to find file:/textures/ui/cybran/icons/units/ura0001o_icon.dds
debug: [uiutil.lua, function UIFile()] - Unable to find file:/textures/ui/cybran/icons/units/ura0002o_icon.dds
debug: [uiutil.lua, function UIFile()] - Unable to find file:/textures/ui/cybran/icons/units/ura0003o_icon.dds
debug: [uiutil.lua, function UIFile()] - Unable to find file:/textures/ui/cybran/icons/units/ura0004_icon.dds
debug: [uiutil.lua, function UIFile()] - Unable to find file:/textures/ui/cybran/icons/units/zxa0001_icon.dds
info: Hooked /lua/ui/game/selection.lua with /schook/lua/ui/game/selection.lua
info: creating high fidelity terrain
info: creating high fidelity water
info: Hooked /lua/ui/game/minimap.lua with /schook/lua/ui/game/minimap.lua
info: range_RenderHighlighted true
info: range_RenderSelected true
info: range_RenderBuild true
info: creating high fidelity terrain
info: creating high fidelity water
info: res_AfterPrefetchDelay 100
info: res_PrefetcherActivityDelay 1
info: net_lag 0
info: ui_RenderCustomNames 0
info: UI_ForceLifbarsOnEnemy 0
info: SC_FrameTimeClamp 10
info: /savereplay
warning: GetResource: Invalid name ""
info: Can't find texture "" -- trying fallback.
warning: GetResource: Invalid name ""
info: Can't find texture "" -- trying fallback.
warning: GetResource: Invalid name ""
info: Can't find texture "" -- trying fallback.
info: Exe Version: 1.0
debug: Current gametime: 00:00:00
info: Exe Version: 1.0
info: Exe Version: 1.0
info: Exe Version: 1.0
info: Exe Version: 1.0
info: Exe Version: 1.0
info: Exe Version: 1.0
info: Exe Version: 1.0
info: Exe Version: 1.0
info: playable area coordinates are { 0, 0, 1024, 1024 }
info: Offmapareas are {
info: { x0=-100, x1=1124, y0=-100, y1=0 },
info: { x0=-100, x1=1124, y0=1024, y1=1124 },
info: { x0=-100, x1=0, y0=0, y1=1024 },
info: { x0=1024, x1=1124, y0=0, y1=1024 }
info: }
info: Cam_Free
... ?
Log or error message I’m not sure what to share here.
Expected behavior Information regarding the crash, appended to the log. An example:
Command line:
ForgedAlliance.exe /init "init-dev.lua" /EnableDiskWatch /showlog /log test.log
Exit code: 0
Game version: 3731
Game tick: 0
C++ Exceptions:
.?AUlua_RuntimeError@@
@c:\users\jip\documents\supreme commander\fa\lua\ui\menus\main.lua 310
String:access to nonexistent global variable "LUA_PATH", Float:2, String:access to nonexistent global variable "LUA_PATH"
stack traceback:
[C]: in function `error'
...alliance\gamedata\mohodata.scd\lua\system\config.lua(53): in function <...alliance\gamedata\mohodata.scd\lua\system\config.lua:52>
[C]: ?
...\documents\supreme commander\fa\lua\system\dkson.lua(52): in function <...\documents\supreme commander\fa\lua\system\dkson.lua:49>
[C]: in function `pcall'
...\documents\supreme commander\fa\lua\system\dkson.lua(49): in main chunk
[C]: in function `doscript'
[C]: ?
...documents\supreme commander\fa\lua\system\import.lua(87): in function `import'
...documents\supreme commander\fa\lua\system\import.lua(72): in function `import'
...ocuments\supreme commander\fa\lua\ui\lobby\lobby.lua(47): in main chunk
[C]: in function `doscript'
[C]: ?
...documents\supreme commander\fa\lua\system\import.lua(87): in function `import'
...documents\supreme commander\fa\lua\system\import.lua(72): in function `import'
...documents\supreme commander\fa\lua\ui\menus\main.lua(835): in function `StartLobby'
...documents\supreme commander\fa\lua\ui\menus\main.lua(840): in function <...documents\supreme commander\fa\lua\ui\menus\main.lua:832>
...documents\supreme commander\fa\lua\ui\menus\main.lua(749): in function <...documents\supreme commander\fa\lua\ui\menus\main.lua:741>
...documents\supreme commander\fa\lua\ui\menus\main.lua(310): in function <...documents\supreme commander\fa\lua\ui\menus\main.lua:295>
DLLs:
(...)
OS Windows
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Diagnosing issues using crash reports and device logs
To debug a problem using a crash report: Build your app with symbol information and retain the Xcode archive before distributing the app....
Read more >How To Debug A Crash When The Crash Report Is Corrupted
These are the steps we recommended the developers take to fix the bug: Discover which background task in your app is overrunning CPU/wall...
Read more >Guidelines and HOWTOs/Debugging/How to create useful ...
A good crash report at Bugzilla consists of two parts: a description of how to reproduce the crash and a backtrace of the...
Read more >I can't see the crash report. BreakDebuggerAsyncSafe()
Once you have loaded the crash dump into windbg and got your symbol server paths sorted out (which you have done) you need...
Read more >Understanding and Analyzing Application Crash Reports - zzfx
When an application crashes, a crash report is created and stored on the device. Crash reports describe the conditions under which the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed the errors. When starting from the client, garbage appears in the log(%USER%, %USER_PROFILE%). game_16200742.log
As a note the crash detailed by Jip does not appear to be detected by the debugger at all