Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash report missing of debugger #2538

Closed
Garanas opened this issue Jan 23, 2022 · 7 comments
Closed

Crash report missing of debugger #2538

Garanas opened this issue Jan 23, 2022 · 7 comments
Labels

Comments

@Garanas
Copy link
Member

Garanas commented Jan 23, 2022

Describe 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:

image

Then enable free camera (CTRL + V by default) and orientate your camera like in this screenshot:

image

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

@Garanas Garanas added the bug label Jan 23, 2022
@Sheikah45
Copy link
Member

I am not sure why it is not being appended. Can you check that the commands are being run properly?

@Sheikah45
Copy link
Member

As a note the crash detailed by Jip does not appear to be detected by the debugger at all

@Garanas
Copy link
Member Author

Garanas commented Jan 23, 2022

I'm hoping to come across a crash that is properly detected 😃

@KionX
Copy link

KionX commented Jan 24, 2022

Fixed the errors.
When starting from the client, garbage appears in the log(%USER%, %USER_PROFILE%).
game_16200742.log

@Garanas
Copy link
Member Author

Garanas commented Jan 27, 2022

This issue can be closed - just tested and confirmed it.

@Garanas Garanas closed this as completed Jan 27, 2022
@Sheikah45
Copy link
Member

That isn't garbage the client just removes the user name and directory and replaced it with %USER% I guess you're username is just x

@KionX
Copy link

KionX commented Jan 28, 2022

This is true. But should apply it more carefully. There are no names in the debugger report.
Replaced the letters and not the words. Perhaps it should be done so as not to replace sequences of less than 3 letters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants