[Bug 5451] Diablo 1.0x crashes with fault on write access

[Wine Bugs]

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





------- Additional Comments From saulius.krasuckas at elst.vtu.lt  2006-17-06 03:27 -------
Created an attachment (id=2659)
 --> (http://bugs.winehq.org/attachment.cgi?id=2659&action=view)
Debugger session (empyt line inserted before every debugger prompt occurrence)

It looks strange for me that during first break at IDirectDrawSurfaceImpl_Lock
I see backtrace ending in kernel32 and libwine.so.1:

  5 0x0040df48 in diablo_s (+0xdf48) (0x0040df48)
  6 0x0046321e in diablo_s (+0x6321e) (0x0046321e)
  7 0x7fc71461 start_process+0xbd ... in kernel32 (0x7fc71461)
  8 0xb7f271cb wine_switch_to_stack+0x17 in libwine.so.1 (0xb7f271cb)

But during second break backtrace ends already in ddraw and native storm.dll:

  2 0x7d5786c2 IDirectDrawSurface3Impl_Lock+0x2e ... in ddraw (0x7d5786c2)
  3 0x15009995 in storm (+0x9995) (0x15009995)

I thought maybe TID has changed, but "info th" tells it's always == 00000011:

 process  tid	   prio (all id:s are in hex)
 00000010 (D) Z:\mnt\antras\__\Diablo\Spawn\Diablo_s.exe
	 00000011    0 <==
 ...
 00000010 (D) Z:\mnt\antras\__\Diablo\Spawn\Diablo_s.exe
	 00000014   15
	 00000013   15
	 00000011    0 <==

-- 
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.