gdiplus benefits from valgrind testing when running DNS 9.0

[Nikolay Sivov]

Susan Cragin wrote:
> I tried installing and running Dragon NaturallySpeaking 9.0 yesterday with wine's gdiplus. 
> wine-1.1.0
>
> The program installed well, and training worked, too. Recognition during training was fast enough to keep up. Running it worked up to a point, but when it finally crashed I was trying something that doesn't always work anyway. 
>
> Here are the install gdiplus warnings:
>
> fixme:gdiplus:GdipSetLinePresetBlend not implemented
>
> fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
>
> fixme:shell:SHAppBarMessage msg=6, data={cb=36, hwnd=0x60058, callback=7c80a46c, edge=2081853302, rc=(589886,13361216)-(2081853346,13361216), lparam=cc00b0}: stub
>
> fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
>
> fixme:shell:SHAppBarMessage msg=2, data={cb=36, hwnd=0x60058, callback=7c1520e1, edge=1, rc=(0,0)-(800,28), lparam=ffffffec}: stub
>
> fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
>
> err:ntdll:RtlpWaitForCriticalSection section 0xcc3bb8 "?" wait timed out in thread 00dd, blocked by 005e, retrying (60 sec)
>
> fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
>
> fixme:shell:SHAppBarMessage msg=6, data={cb=36, hwnd=0x60058, callback=cbf41c, edge=2081853302, rc=(1638456,13361216)-(2081853346,13361216), lparam=cc00b0}: stub
>
> fixme:shell:SHAppBarMessage msg=6, data={cb=36, hwnd=0x60058, callback=cbf470, edge=2081853302, rc=(1638456,13361216)-(2081853346,13361216), lparam=cc00b0}: stub
>
> fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
>
> fixme:oleacc:AccessibleObjectFromWindow 0x1009a 0 {618736e0-3c3d-11cf-810c-00aa00389b71} 0x33f17c
>
> -------------------------------
> Here are the run warnings:
> -------------------------------
>
> fixme:gdiplus:GdipCreateHBITMAPFromBitmap stub
>
> wine: Call from 0x7b845630 to unimplemented function gdiplus.dll.GdipCreateLineBrushFromRectWithAngleI, aborting
>
>
> err:ntdll:RtlpWaitForCriticalSection section 0x7bc932c4 "loader.c: loader_section" wait timed out in thread 00dd, blocked by 003a, retrying (60 sec)
>
> This next one eventually crashed the program. 
>   
Don't follow you. Looks like the bug 13173 remains the same. Or 
something changed with 1.1.0?