d3d9/tests: Use wine_dbgstr_rect() to print RECTs.

[Michael Stefaniuc]

On 06/10/2016 10:44 AM, Marvin wrote:
> While running your changed tests on Windows, I think I found new failures.
> Being a bot and all I'm not very good at pattern recognition, so I might be
> wrong, but could you please double-check?
> Full results can be found at
> https://testbot.winehq.org/JobDetails.pl?Key=23495
> 
> Your paranoid android.
> 
> 
> === w864 (64 bit device) ===
> device.c:4351: Test failed: cw is 0xf60, expected 0x7f.
> device.c:4360: Test failed: Callback cw is 0xf60, expected 0x7f.
> 
> === w1064 (64 bit device) ===
> device.c:4351: Test failed: cw is 0xf60, expected 0x7f.
> device.c:4360: Test failed: Callback cw is 0xf60, expected 0x7f.
This are existing failures.


> === w1064 (32 bit d3d9ex) ===
> d3d9ex.c:2351: Test failed: Got unexpected hr 0, i=0.
> d3d9ex.c:2353: Test failed: Got unexpected hr 0, i=0.
> d3d9ex.c:2351: Test failed: Got unexpected hr 0, i=1.
> d3d9ex.c:2353: Test failed: Got unexpected hr 0, i=1.
> 
> === w1064 (64 bit d3d9ex) ===
> d3d9ex.c:2351: Test failed: Got unexpected hr 0, i=0.
> d3d9ex.c:2353: Test failed: Got unexpected hr 0, i=0.
> d3d9ex.c:2351: Test failed: Got unexpected hr 0, i=1.
> d3d9ex.c:2353: Test failed: Got unexpected hr 0, i=1.
This ones are odd. The tests shows consistent 4 failures for win10 too
but in an other spot/test function at lines 157[2468].
A whitespace only change produces the exact same pattern as my patch so
this are unrelated https://testbot.winehq.org/JobDetails.pl?Key=23501

bye
	michael