https://bugs.winehq.org/show_bug.cgi?id=45586
Bug ID: 45586 Summary: Empyrion Dedicated generates err:seh:setup_exception stack overflow Product: Wine Version: 3.13 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: kovus@soulless.wtf
Created attachment 62007 --> https://bugs.winehq.org/attachment.cgi?id=62007 wine debug output
Empyrion Dedicated server ("nographics" as they call it) generates an err:seh:setup_exception when you try to run it.
0009:err:seh:setup_exception stack overflow 2896 bytes in thread 0009 eip 000000007bc9188d esp 0000000000130ac0 stack 0x130000-0x132000-0x230000
Per a suggestion from https://forum.winehq.org/viewtopic.php?f=2&t=30972, I'm posting the requested information here.
Wine 3.13 (built from the FreeBSD ports tree as "wine-devel") 64-bit Fresh .wine folder (deleted and recreated with defaults when running winecfg).
Commands used to generate the attached output (tcsh) setenv WINEPATH . setenv WINEDEBUG +timestamp,+tid,+all wine64 EmpyrionDedicated.exe -batchmode -nographics -logFile Logs/temp.log | & tee ~/wine_empyrion_server_log.txt
The error mentioned in the subject is on line 617399 of the attached log. After that, EmpyrionDedicated goes into what appears to be an infinite loop, so the file ends when the program gets ctl+c'd.
https://bugs.winehq.org/show_bug.cgi?id=45586
--- Comment #1 from Kovus kovus@soulless.wtf --- I realized I had failed to include any information about getting Empyrion's dedicated server.
Official directions are on https://empyrion.gamepedia.com/Dedicated_Server_Setup
How I installed it: Installed Linux steamcmd steamcmd +runscript update_empyrion.txt
// update_empyrion.txt @sSteamCmdForcePlatformBitness 64 @sSteamCmdForcePlatformType windows login anonymous force_install_dir ../empyrion/ app_update 530870 validate exit
https://bugs.winehq.org/show_bug.cgi?id=45586
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x@gmail.com
--- Comment #2 from Louis Lenders xerox.xerox2000x@gmail.com --- Hi, this is more or less a guess but maybe it chokes ecause of missing registrykeys,
You might try see what the following keys look like in windows and add them using wine`s regedit.
keys it tries to find: HKLM\Hardware\description\System\SystemBiosVersion HKLM\Hardware\description\System\VideoBiosVersion
HKLM\SYSTEM\ControlSet001\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000
From your log:
426439.448:0008:0009:Call advapi32.RegOpenKeyA(80000002,141ac07a0 "SYSTEM\ControlSet001\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000",141ac0 87e) ret=141ac5548 426439.448:0008:0009:Ret advapi32.RegOpenKeyA() retval=00000002 ret=141ac5548
426439.448:0008:0009:Call advapi32.RegOpenKeyA(80000002,141ac083f "Hardware\description\System",141ac087e) ret=141ac592f 426439.448:0008:0009:Ret advapi32.RegOpenKeyA() retval=00000000 ret=141ac592f 426439.448:0008:0009:Call advapi32.RegQueryValueExA(00000110,141ac085b "SystemBiosVersion",00000000,00000000,141ac0886,141ac0a86) ret=141ac5a41 426439.448:0008:0009:Ret advapi32.RegQueryValueExA() retval=00000002 ret=141ac5a41
426439.449:0008:0009:Call advapi32.RegQueryValueExA(00000110,141ac086d "VideoBiosVersion",00000000,00000000,141ac0886,141ac0a86) ret=141ac5baf 426439.449:0008:0009:trace:reg:RegQueryValueExA (0x110,"VideoBiosVersion",0x0,0x0,0x141ac0886,0x141ac0a86=512) 426439.449:0008:0009:Ret advapi32.RegQueryValueExA() retval=00000002 ret=141ac5baf
426439.449:0008:0009:Call advapi32.RegQueryValueExA(00000110,141ac085b "SystemBiosVersion",00000000,00000000,141ac0886,141ac0a86) ret=141ac5d26
https://bugs.winehq.org/show_bug.cgi?id=45586
--- Comment #3 from Kovus kovus@soulless.wtf --- Thanks for the suggestion. Just to make sure that I wasn't imagining when I tried something similar before (as I'd see those on one of the other output logs I'd encountered), I took these steps to try to make it work:
Exported HKLM\Hardware\Description\System from a working Windows machine, as it had both SystemBiosVersion & VideoBiosVersion defined. Trimmed out all the sub-key information leaving me a reg file that was just the few related keys.
# cat hklm_sys.reg ��Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System] "SystemBiosDate"="10/01/12" "SystemBiosVersion"=hex(7):48,00,50,00,20,00,20,00,20,00,20,00,20,00,2d,00,20,\ 00,32,00,30,00,31,00,32,00,31,00,30,00,30,00,31,00,00,00,00,00 "VideoBiosDate"="01/22/07" "VideoBiosVersion"=hex(7):56,00,47,00,41,00,2f,00,56,00,42,00,45,00,20,00,42,\ 00,49,00,4f,00,53,00,2c,00,20,00,56,00,65,00,72,00,73,00,69,00,6f,00,6e,00,\ 20,00,56,00,33,00,2e,00,38,00,53,00,4c,00,00,00,52,00,65,00,76,00,69,00,73,\ 00,69,00,6f,00,6e,00,3a,00,20,00,30,00,2e,00,33,00,33,00,20,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,00,00
Copied that to the machine I'm trying this on, as "hklm_sys.reg"
Ran: # setenv WINEPATH . # wine64 cmd Z:\home\joe\games\empyrion> regedit /C hklm_sys.reg Z:\home\joe\games\empyrion> EmpyrionDedicated.exe -nographics -batchmode -logFile logs/test.log 0030:err:seh:setup_exception stack overflow 2896 bytes in thread 0030 eip 000000007bc9023c esp 0000000000140ac0 stack 0x140000-0x142000-0x240000
I could not figure out how to get wine64 to remember those registry keys between wine64 launches (to do regedit & empyrion in two separate wine64 commands), which is why I imported the reg file & ran empyrion from inside a wine64 cmd prompt.
-
wine-bugs＠winehq.org