2017-03-22 10:31 GMT+01:00 Peter Uhnak <i.uhnak@gmail.com>:
Hi,

Originally I thought my VM is crashing because of FT, so I applied some fix from FogBugz (that is now part of Pharo 6), but that didn't help.

So I disabled FT in settings and changed fonts to non-FT ones; didn't help.
So I completely removed FT2Plugin.dll (now settings just states that FT fonts are not available), but that didn't help either.

And obviously there is no crash.dmp whatsoever (this is latest Windows VM).

This crash is extremely frustrating because the crash happens _during saving_, which means I am losing code all the time and have to constantly recover them, which really makes my blood boil.

Without crash dump I don't even know where and how to start investigating. Windows kindly opens Visual Studio when Pharo crashes, but all it shows to me is assembly, which is not very useful to me. I can somewhat orient myself in the C code of the VM (as I've alredy fixed some other issues in the VM), but here I am lost.

<SNIP>
00407D7F�� ret
00407D80�� mov�� �� �� �� ��eax,dword ptr ds:[00596E44h]
00407D85�� test�� �� �� �� al,3
00407D87�� jne�� �� �� �� ��00407DB2
00407D89�� mov�� �� �� �� ��ecx,dword ptr ds:[596E08h]
00407D8F�� lea�� �� �� �� ��edx,[ecx-1]
00407D92�� cmp�� �� �� �� ��eax,edx
00407D94�� jb�� �� �� �� �� 00407DB2
00407D96�� cmp�� �� �� �� ��dword ptr ds:[596E10h],eax
00407D9C�� jb�� �� �� �� �� 00407DB2
00407D9E�� mov�� �� �� �� ��ecx,dword ptr ds:[5B89D0h]
00407DA4�� cmp�� �� �� �� ��dword ptr [eax-4],ecx
00407DA7�� jb�� �� �� �� �� 00407DB2
00407DA9�� mov�� �� �� �� ��eax,dword ptr ds:[00596E28h]
---> 00407DAE�� movzx�� �� �� ��eax,byte ptr [eax]
00407DB1�� ret

eax = 00000000
ecx = 04700000
</SNIP>

So my question I guess is:
How can we fix this? How can I help fix this? Because I've lost countless days of time and energy on this f***ing problem...

Peter


Maybe it would help if other people try to reproduce this error.
Can you share the image/code you are using ?

Do you have a mingw build environment ? Sometimes it helps to start the vm with gdb, and if an exception occurs that does not write a crash.dmp, if you are lucky, gdb will show some additional information.


(for me, the latest windows vm *sometimes* does create a crash.dmp).