4.2.0-25 crash with ShadowGDI(Any resolution)

[Harold L Hunt II]

Derrick,

That is really strange.  the biHeight memeber of the DIBSECTION 
structure is passed in as a negative, but Windows sets it back to a 
positive when the DIB is created.  In your case the DIB is being created 
but the height sign is not being toggled back to positive.  I don't know 
if the solution to this is easy or hard, but I have a start.  That start 
is just to toggle the sign back when computing the stride (which you 
will notice is being reported as zero)... this should at least result in 
the correct stride being calculated.

Try this executable and send in your log file/results:

http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test77-DEBUG-2.exe.bz2 
(1202 KiB)

Harold

Derrick Jobidon wrote:
> Have WIndows 98 (not SE). the x server will always crash with ShadowGDI.
> My video card is a ATI AIW-128. I noticed the height: -811 in the log
> and wondered if the problem could be around there. Here isthe
> stackdump from test77 binaries
> from the website and the log.
> 
> Exception: STATUS_ACCESS_VIOLATION at eip=00465CC3
> eax=00000000 ebx=102B90F0 ecx=102B90F0 edx=00000010 esi=00000000
> edi=00000001
> ebp=00ABFA48 esp=00ABF9E8
> program=C:\CYGWIN\USR\X11R6\BIN\XWIN.EXE
> cs=016F ds=0177 es=0177 fs=5787 gs=0000 ss=0177
> Stack trace:
> Frame     Function  Args
> 00ABFA48  00465CC3  (00000000, 00000000, 00000000, 102B90F0)
> 00ABFAB8  0046B603  (10100A40, 102B90B0, 102B98F8, 00ABFBD0)
> 00ABFB48  0046BCA8  (10100A40, 102B90B0, 102B98F8, 00ABFBD0)
> 00ABFBF8  0046C1E3  (10100A40, 102B90B0, 102B98F8, 0000022E)
> 00ABFC38  0046C3EE  (10100A40, 102B90B0, 102B98F8, 0000022E)
> 00ABFC78  0047F30E  (100F7118, 0000022E, 00000186, 00000020)
> 00ABFCA8  004A0CDA  (100F7118, 102BD610, 0000023D, 00000195)
> 00ABFCE8  0047A5A3  (10100A40, 0000047A, 00ABFD28, 00417B0E)
> 00ABFCF8  0047A23B  (100F7118, 102BD610, 00000195, 00000000)
> 00ABFD28  00417B0E  (10100A40, 00000000, 615E1EAC, 00000000)
> 00ABFD68  00401774  (00000003, 615E1EAC, 100F0328, 00ABFD9C)
> 00ABFDB8  610073E8  (610C39E8, FFFFFFFE, 00000008, 610C390C)
> 00ABFE08  610076CD  (00000000, 00000000, BFFC9490, 00ABFF78)
> 00ABFE28  006FCC52  (00401490, 037F2330, 00ABFF78, BFF8B537)
> 00ABFE38  0040103C  (00000000, 817722D0, 008B0000, 6E697758)
> 00ABFF78  BFF8B537  (88428284, 817722D0, 00000008, 00000000)
> End of stack trace (more stack frames may be present)
> 
> ddxProcessArgument - Initializing default screens
> winInitializeDefaultScreens - w 1152 h 864
> winInitializeDefaultScreens - Returning
> OsVendorInit - Creating bogus screen 0
> (EE) Unable to locate/open config file
> InitOutput - Error reading config file
> winDetectSupportedEngines - Windows 95/98/Me
> winDetectSupportedEngines - DirectDraw installed
> winDetectSupportedEngines - DirectDraw4 installed
> winDetectSupportedEngines - Returning, supported engines 00000017
> InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
> winSetEngine - Using user's preference: 1
> winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per
> pixel
> winCreateBoundingWindowWindowed - User w: 1152 h: 864
> winCreateBoundingWindowWindowed - Current w: 1152 h: 864
> winAdjustForAutoHide - Original WorkArea: 0 0 836 1152
> winAdjustForAutoHide - Adjusted WorkArea: 0 0 836 1152
> winCreateBoundingWindowWindowed - WindowClient w 1146 h 811 r 1146 l 0 b
> 811 t 0
> winCreateBoundingWindowWindowed -  Returning
> winAllocateFBShadowGDI - Creating DIB with width: 1146 height: 811 depth:
> 16
> winAllocateFBShadowGDI - Dibsection width: 1146 height: -811 depth: 16
> size image: 1858812
> winAllocateFBShadowGDI - Created shadow stride: 0
> winFinishScreenInitFB - Masks: 0000f800 000007e0 0000001f
> 
>