[Bug 740] Changed - divide by zero exception in x11drv.dll

[wine-bugs at winehq.com]

http://bugs.winehq.com/show_bug.cgi?id=740

*** shadow/740	Thu May 30 17:11:48 2002
--- shadow/740.tmp.18864	Thu May 30 19:11:33 2002
***************
*** 169,171 ****
--- 169,208 ----
  an attachement; Note that it's longer than just the last 
  few 100 lines, since the last
  lines have more to do with the debugger not working rather than the problem.
+ 
+ ------- Additional Comments From tony_lambregts at telusplanet.net  2002-05-30 19:11 -------
+ Sorry for the "EDT"/"EST" mixup. Looks like this is the patch for sure then.
+  
+ trace:cursor:X11DRV_GetCursorPos pointer at (393,497)
+ 0806c0a0:Ret  x11drv.GetCursorPos() retval=000001f1 ret=4077f8e3
+ 0806c0a0:Ret  user32.GetCursorPos() retval=00000001 ret=0086d98b
+ 0806c0a0:Call user32.ScreenToClient(00010027,405c60e8) ret=0086d99d
+ 0806c0a0:Ret  user32.ScreenToClient() retval=00000001 ret=0086d99d
+ 0806c0a0:Call user32.SetCursor(0000036e) ret=0087165c
+ trace:cursor:SetCursor 036e
+ 0806c0a0:Call x11drv.SetCursor(4040ba78) ret=407737ae
+ trace:cursor:X11DRV_GetCursor Bitmap 32x32 planes=1 bpp=24 bytesperline=96
+ 
+ this corresponds to the code introduced by the patch. The trace is downhill
+ after this...
+ 
+ 0806c0a0:Call kernel32.GetLastError() ret=0085af89
+ 0806c0a0:Ret  kernel32.GetLastError() retval=00000006 ret=0085af89
+ 0806c0a0:Call kernel32.TlsGetValue(00000009) ret=0085af97
+ 0806c0a0:Ret  kernel32.TlsGetValue() retval=4183001c ret=0085af97
+ 0806c0a0:Call kernel32.SetLastError(00000006) ret=0085afe3
+ 0806c0a0:Ret  kernel32.SetLastError() retval=00000006 ret=0085afe3
+ 0806c0a0:Call kernel32.UnhandledExceptionFilter(404b490c) ret=00860e1d
+ 0806c0a0:Call kernel32.IsBadCodePtr(102092e0) ret=00861446
+ 0806c0a0:Ret  kernel32.IsBadCodePtr() retval=00000000 ret=00861446
+ 0806c0a0:Call kernel32.IsBadCodePtr(7800b4fb) ret=10209401
+ 0806c0a0:Ret  kernel32.IsBadCodePtr() retval=00000000 ret=10209401
+ wine: Unhandled exception, starting debugger...
+ 
+ David, how do you feel about adding some traces to the code to narrow down the
+ problem. To do this all you need to do is add something like this to the code
+ 
+  TRACE("Got this far \n") 
+ 
+ If you don't feel comfortable with that then I will see about working up a patch
+  for you.