According to Stefans suggestion I have implemented a test for the string copies into the identifier structure. Test is designed to fail to give me a hint what is going on. Hopefully someone can post the results of a test run in native environment.
Thank you
On Tue, Oct 13, 2009 at 6:20 PM, Markus Stockhausen markus.stockhausen@collogia.de wrote:
According to Stefans suggestion I have implemented a test for the string copies into the identifier structure. Test is designed to fail to give me a hint what is going on. Hopefully someone can post the results of a test run in native environment.
Thank you
Vista SP1: ddrawmodes.c:670: Test failed: last bytes of szDriver string are 00000000 ddrawmodes.c:671: Test failed: last bytes of szDescription string are 00000000
On 10/13/2009 09:20 AM, Markus Stockhausen wrote:
ok(1==0, "last bytes of szDriver string are %08x\n", dddi2[0x7f]);
Hi Markus,
You know that you can use trace() for that?
Windows XP SP3 (real box):
ddrawmodes.c:670: Test failed: last bytes of szDriver string are 00000000 ddrawmodes.c:671: Test failed: last bytes of szDescription string are 00000000
Am 13.10.2009 um 09:20 schrieb Markus Stockhausen:
ok(1==0, "last bytes of szDriver string are %08x\n",
dddi2[0x7f]);
ok(1==0, "last bytes of szDescription string are %08x
\n", dddi2[0xff]); Note that you can only test these parts if strlen(pddi.*) indicates that the string content doesn't already reach these bytes(including the terminating null)