[Bug 2615] Myst crashes with latest CVS

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=2615





------- Additional Comments From dclark at akamail.com  2005-01-01 12:48 -------
Neither of you mentioned where of how this is crashing. I spent a little time
looking at Myst, and see rather odd (to me) symptoms. What I see is that for
Wine compiled under RH 9 on two different machines, Myst can generally play the
intro, but crashes upon attempting to actually enter the game. This occurs for
me with CVS versions going back to Oct 03, before which Wine does not run for me
on RH 9 (I think maybe this was when the pthread work was done?). The backtraces
from the traces do not look real. But the relay traces up to the crash generally
look like:
0009:Call hook proc 0x43ca95 (id=WH_GETMESSAGE,code=0,wp=00000001,lp=40733d78)
  ... code deleted.
  0009:Call winmm.timeGetTime() ret=0043cb02
    0009:Call kernel32.GetTickCount() ret=409302d5
    0009:Ret  kernel32.GetTickCount() retval=00008ac8 ret=409302d5
  0009:Ret  winmm.timeGetTime() retval=00008ac8 ret=0043cb02
  0009:Call kernel32.UnhandledExceptionFilter(407355c8) ret=00441195

It appears that there is no problem with the timeGetTime calls... it has been
called from the same place many times previously without crashing. Normally at
this point another call to timeGetTime would be made; Myst seems to always call
the function twice. 

I don't really know how to go about debugging this. Since this error appears in
all versions of runable Wine on two different RH9 machines, I cannot narrow it
down with a regression test. The backtraces appear to show junk, and I don't
really know how to go about getting additional info.

I have a third machine with RH7.3. This one behaves rather different. Myst seems
to work pretty well with a lot of CVS versions, but various bugs are introduced
(and sometimes fixed) with different CVS versions. With a current CVS version,
Myst seems to be prone to random freezes for me (but it doesn't crash). I'm
going through to see whether I can at least find that, since it is definitely an
introduced error.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.