https://bugs.winehq.org/show_bug.cgi?id=37218
Anastasius Focht focht@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@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