On Thu, 2002-10-03 at 16:24, Miguel Feitosa wrote: > try > wine --debugmsg +relay
Hi Miguel. Thanks for you quick reply! I just did the above and have the results. > and see if you have [like I did] a situation where > > 1) A new window call was succesffully executed, a handle was assigned > > 2) A call that does something with the window gets executed and fails > with an invalid window handle exception. > > This was repeated in all the apps I tried. I'm afraid that I don't know how to interpret what I have :(. Here is what appears to be looping: 08ec96c8:Call USER.109: PEEKMESSAGE(0487:e792,0000,0000,0000,0001) ret=05bf:24ed ds=05d7 08ec96c8:Call x11drv.MsgWaitForMultipleObjectsEx(00000000,00000000,00000000,00000000,00000000) ret=406f5146 08ec96c8:Call kernel32.WaitForMultipleObjectsEx(00000000,00000000,00000000,00000000,00000000) ret=4090873b 08ec96c8:Ret kernel32.WaitForMultipleObjectsEx() retval=00000102 ret=4090873b 08ec96c8:Ret x11drv.MsgWaitForMultipleObjectsEx() retval=00000102 ret=406f5146 08ec96c8:Call kernel32._ConfirmSysLevel(40725b9c) ret=406d4c63 08ec96c8:Ret kernel32._ConfirmSysLevel() retval=00000000 ret=406d4c63 08ec96c8:Call kernel32.GetThreadQueue16(00000000) ret=406cb82d 08ec96c8:Ret kernel32.GetThreadQueue16() retval=000004f7 ret=406cb82d 08ec96c8:Call kernel32.GlobalLock16(000004f7) ret=406cb85e 08ec96c8:Ret kernel32.GlobalLock16() retval=40315f00 ret=406cb85e 08ec96c8:Call kernel32.GetThreadQueue16(00000000) ret=406cb82d 08ec96c8:Ret kernel32.GetThreadQueue16() retval=000004f7 ret=406cb82d 08ec96c8:Call kernel32.GlobalLock16(000004f7) ret=406cb85e 08ec96c8:Ret kernel32.GlobalLock16() retval=40315f00 ret=406cb85e 08ec96c8:Call kernel32.ReleaseThunkLock(40e12a70) ret=406f51b4 08ec96c8:Ret kernel32.ReleaseThunkLock() retval=00000000 ret=406f51b4 08ec96c8:Call kernel32.RestoreThunkLock(00000002) ret=406f51c7 08ec96c8:Ret kernel32.RestoreThunkLock() retval=00000000 ret=406f51c7 08ec96c8:Ret USER.109: PEEKMESSAGE() retval=0000 ret=05bf:24ed ds=05d7 This block (I don't know if I caught the start or not) appears to loop indefinitely until I hit CTRL-C. It generated over 60 MB of logs in just a few seconds. Each iteration the values above appear to be exactly the same. > Something between 1 and 2 was corrupting the windows. > The window did start rendering though. I never have seen anything appear on the screen. The program's installer worked just fine but the program itself has yet to draw anything under Wine. > Sorry not to be specific , the wine history pages may > have some of the emails I sent at the time [march-02]. I will do some research and see what I come up with. > Send me some logs and I will try to remember if they > have the same problem that I had.. Well, as I said above, it's about 60 MB. Although I'm sure I could trim it down if I cut out everything after it began looping I still think it would be quite large. If you are still interested I will try to clean it up a little, bzip it and send it your way. Thanks very much for the help. Sean
