[Bug 37218] New: Assertion fail while starting Unity3d
https://bugs.winehq.org/show_bug.cgi?id=37218 Bug ID: 37218 Summary: Assertion fail while starting Unity3d Product: Wine Version: 1.7.25 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: bique.alexandre(a)gmail.com Created attachment 49489 --> https://bugs.winehq.org/attachment.cgi?id=49489 crash log Wine crashes with the following assertion fail: Files\Unity\Editor\Unity.exe: ../../../wine/dlls/dbghelp/symbol.c:282: symt_new_function: Assertion `!sig_type || sig_type->tag == SymTagFunctionType' failed. See the the attached log for more details. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37218 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://unity3d.com/unity/do | |wnload/download-windows CC| |focht(a)gmx.net Component|dbghelp |-unknown --- Comment #1 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, I installed the app with required .NET Framework 3.x/4.x prerequisites and it starts fine here. --- snip --- wine: cannot find L"C:\\windows\\Microsoft.NET\\Framework\\v4.0.30319\\mscorsvw.exe" fixme:service:scmdatabase_autostart_services Auto-start service L"clr_optimization_v4.0.30319_32" failed to start: 2 fixme:exec:SHELL_execute flags ignored: 0x00000100 fixme:exec:SHELL_execute flags ignored: 0x00004100 err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. --- snip --- You obviously have a broken prefix -> bug is invalid. Install the app in a new(!) 32-bit WINEPREFIX with .NET Framework 3.5.x and 4.0 *properly* installed prior and fix missing host prerequisites. Also make sure you followed appdb howtos/notes: https://appdb.winehq.org/objectManager.php?sClass=version&iId=30451 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37218 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|-unknown |dbghelp Summary|Assertion fail while |Unity3D 4.x crash handler |starting Unity3d |causes assertion in Wine's | |PDB parser with app | |provided debug symbols in | |PDB format Ever confirmed|0 |1 --- Comment #2 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, although I can't reproduce your crash I can at least confirm that Wine's PDB parser chokes on the PDB files shipped with Unity. I had the pleasure to debug some nasty random freeze (Mono is always up for surprises) and 'dbghelp' does indeed not like those PDBs, hence they have to be renamed or moved out of the way: --- snip --- $ pwd /home/focht/wine-apps/unity3d/drive_c/Program Files/Unity/Editor $ ls -la *.pdb -rw-rw-r--. 1 focht focht 7130112 Nov 18 17:37 mono.pdb -rw-rw-r--. 1 focht focht 171617280 Nov 18 17:56 Unity.pdb --- snip --- There are a few other PDB related bugs though, such as bug 34990 NOTE: Fixing the assert() problem won't probably help you since it's triggered by some crash elsewhere. Used the following 'winetricks' extension verb: https://github.com/Unity3D-Wine-Support/Unity3D-on-Wine/blob/master/unity3d.... --- snip --- $ winetricks --no-isolate -q unity3d --- snip --- $ sha1sum UnitySetup-4.6.0.exe 5cc7a85e186c965d230bcc7a2a463d92fbc2f7fc UnitySetup-4.6.0.exe $ du -sh UnitySetup-4.6.0.exe 1.3G UnitySetup-4.6.0.exe $ wine --version wine-1.7.34-74-gcf92569 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37218 --- Comment #3 from Anastasius Focht <focht(a)gmx.net> --- Created attachment 50511 --> https://bugs.winehq.org/attachment.cgi?id=50511 WINEDEBUG=+dbghelp_msc,+dbghelp winedbg ./Unity.exe Hello folks, attached is a log with of winedbg output with Unity being run loaded (uncompressed size: 19MB). Unfortunately I couldn't use 'dbghelp_symt' channel as it causes an early abort due to debugstr buffer overflow (C++/std namespace with overly long debug symbols) --- snip --- $ WINEDEBUG=+dbghelp_msc,+dbghelp winedbg ./Unity.exe 2> winedbg_output.txt WineDbg starting on pid 0024 DbgBreakPoint () at /home/focht/projects/wine/wine.repo/src/include/winternl.h:2017 0x7b8624bc DbgBreakPoint+0x4 [/home/focht/projects/wine/wine.repo/src/include/winternl.h:2017] in kernel32: popl %ebp 2017 static inline void WINAPI DbgBreakPoint(void) { __asm__ __volatile__("int3"); } Wine-dbg>c Thread ID=0031 renamed using MS VC6 extension (name=="UnityWork") Thread ID=0032 renamed using MS VC6 extension (name=="UnityWork") Thread ID=0033 renamed using MS VC6 extension (name=="UnityWork") Thread ID=0037 renamed using MS VC6 extension (name=="UnitySubs") Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x006dd941). Exception 80000101 --- snip --- Regars -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37218 fjfrackiewicz(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fjfrackiewicz(a)gmail.com --- Comment #4 from fjfrackiewicz(a)gmail.com --- Hi, I have a relatively new Unity game that crashes with the same error as described by Alexandre Bique. The game is Necropolis and I believe it is made in Unity 5 and it crashes with the following error in terminal: ../../../wine/dlls/dbghelp/symbol.c:281: symt_new_function: Assertion `!sig_type || sig_type->tag == SymTagFunctionType' failed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37218 --- Comment #5 from fjfrackiewicz(a)gmail.com --- Created attachment 55092 --> https://bugs.winehq.org/attachment.cgi?id=55092 WINEDEBUG=++dbghelp_msc,+dbghelp,+dbghelp_symt wine Necropolis.exe -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37218 --- Comment #6 from fjfrackiewicz(a)gmail.com --- Created attachment 55093 --> https://bugs.winehq.org/attachment.cgi?id=55093 Terminal output Wine 1.9.14 I have attached the terminal output for Wine 1.9.14. The debug log from my previous comment is also from Wine 1.9.14. Unfortunately, I did not use the winetricks unity3d verb. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37218 --- Comment #7 from fjfrackiewicz(a)gmail.com --- Created attachment 57383 --> https://bugs.winehq.org/attachment.cgi?id=57383 Terminal output Wine-2.2-86-g3d62cd26d1 This issue is now affecting a game that previously worked (by "worked" I mean I could get to the loading screen and main menu...) and now it crashes due to this crash handler or whatever. I've attached my terminal output from Wine 2.2-git. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org