<div> <br>
</div>
<div> <br>
</div>
<div> <br>
</div>
-----Original Message-----<br>
From: Lei Zhang <thestig@google.com><br>
To: celticht32@aol.com<br>
Cc: wine-devel@winehq.org<br>
Sent: Tue, 1 Jul 2008 11:34 am<br>
Subject: Re: Possible issue with win.c and help<br>
<br>
<div id="AOLMsgPart_0_5f1a496a-09d9-46e5-b909-416f83a3050b" style="margin: 0px; font-family: Tahoma,Verdana,Arial,Sans-Serif; font-size: 12px; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
<pre style="font-size: 9pt;"><tt>On Mon, Jun 30, 2008 at 9:05 PM, Chris Ahrendt <<a href="mailto:celticht32@aol.com">celticht32@aol.com</a>> wrote:<br>
> Ok in my ever increasing search to figure out why EQ2 is getting a<br>
> unhandled exception and also a no ipixel error. (I am convinced this is<br>
> two separate bugs now)<br>
><br>
> Bug One :<br>
><br>
> This is the unhandled exception:<br>
> If I have EQ2 run in anything but win98 mode (which I don't think is<br>
> supported anymore by EQ2) wine dies with a unhandled exception. If I set<br>
> to win98 it ends with a no ipixel format error message box (the second<br>
> bug) after it begins to draw the window. The other thing is the msg box<br>
> is not a typical msg box saying that something isn't supported but looks<br>
> to be an exception in ClientApp.cpp which means they are getting some<br>
> unhandled exception while drawing the window.<br>
><br>
> What I think might be going on based on this :<br>
><br>
> trace:win:WIN_SetWindowLong 0x2002c 0 0 W<br>
> trace:win:WIN_SetWindowLong Fell Through<br>
> trace:win:WIN_SetWindowLong Release Ptr<br>
> trace:win:WIN_DestroyWindow 0x2002c<br>
> trace:win:WIN_DestroyWindow 0x1002e<br>
> trace:win:WIN_DestroyWindow 0x10030<br>
> trace:win:WIN_DestroyWindow 0x10032<br>
> trace:win:WIN_DestroyWindow 0x10034<br>
> trace:win:WIN_DestroyWindow 0x10036<br>
> trace:win:WIN_DestroyWindow 0x10038<br>
> trace:win:WIN_DestroyWindow 0x1003a<br>
> trace:win:WIN_DestroyWindow 0x1003c<br>
> trace:win:WIN_DestroyWindow 0x1003e<br>
> trace:win:WIN_DestroyWindow 0x10040<br>
> trace:win:WIN_DestroyWindow 0x10042<br>
> trace:win:WIN_DestroyWindow 0x10044<br>
> trace:win:WIN_SetWindowLong 0x2002c 0 0 W<br>
><br>
> ====================================================================<br>
> These are my trace additions in SetWindowLong to help me follow the<br>
> execution of the code<br>
><br>
> trace:win:WIN_SetWindowLong Fell Through<br>
> trace:win:WIN_SetWindowLong Release Ptr<br>
> trace:win:WIN_SetWindowLong 0x2002c 12 0 W<br>
> trace:win:WIN_SetWindowLong Fell Through<br>
> trace:win:WIN_SetWindowLong Server Start Request<br>
> trace:win:WIN_SetWindowLong Default<br>
> trace:win:WIN_SetWindowLong no call Err<br>
> trace:win:WIN_SetWindowLong Default get and Set Win Data<br>
> trace:win:WIN_SetWindowLong Release Ptr<br>
> trace:win:WIN_SetWindowLong Returning 1871960<br>
><br>
> CRASH! Unhandled Exception<br>
><br>
> I think the window is being destroyed in reverse for some reason. Thats<br>
> just my gut first feeling based on the above trace and the exception<br>
> output. This is where my knowledge on Windows behavior ends. Does 98<br>
> destroy the windows chain differently than XP? This would explain why<br>
> the exception doesn't occur in 98 but does in XP.<br>
><br>
> Second Bug:<br>
> This is the ipixel problem which I haven't figured out<br>
> how to debug whats going on there, but think it might be related to<br>
> this error:<br>
><br>
> libGL error: drmMap of framebuffer failed (Cannot allocate memory)<br>
> libGL error: reverting to (slow) indirect rendering<br>
> libGL error: drmMap of framebuffer failed (Cannot allocate memory)<br>
> libGL error: reverting to (slow) indirect rendering<br>
><br>
> Which I am not sure why this is occurring yet but one bug at a time.<br>
> Where would someone look to trace along the window draw chain to see<br>
> where it dies. Some of the debug flags cause my machine to lock up which<br>
> I know is a driver issue and other lockups could be caused by the above<br>
> exception messing something up in X as the disk still runs when that<br>
> lockup occurs but X is DOA.<br>
><br>
> Thoughts????? Ideas???? Suggestions??????<br>
><br>
> Chris<br>
><br>
><br>
><br>
<br>
Hi,<br>
<br>
Please file bug reports on the Wine Bugzilla - <a href="http://bugs.winehq.org/" target="_blank">http://bugs.winehq.org/</a><br>
The second issue looks like 3d graphics are not set up correctly on<br>
your computer. You should ask your favorite Linux forum about that.<br>
</tt><font face="Arial, Helvetica, sans-serif"><br>
<br>
<br>
<br>
<br>
Oh this is already reported as a bug... as to the second I know.. was just looking for some pointers...<br>
<br>
Need help actually understanding the way windows are handled in 98 vs XP .<br>
<br>
The graphic are set up correctly though...<br>
<br>
Chris<br>
</font></pre>
</div>
<!-- end of AOLMsgPart_0_5f1a496a-09d9-46e5-b909-416f83a3050b -->
<div id='u8CAA9ABA5807C60-F4C-4DC' class='aol_ad_footer'><FONT style="color: black; font: normal 10pt ARIAL, SAN-SERIF;"><HR style="MARGIN-TOP: 10px"><A title="http://toolbar.aol.com/moviefone/download.html?ncid=aolcmp00050000000011" href="http://toolbar.aol.com/moviefone/download.html?ncid=aolcmp00050000000011" target="_blank">Get the Moviefone Toolbar</A>. Showtimes, theaters, movie news, & more!</FONT> </div>