Re: [PATCH] kernel32: lstrlen does not call SetLastError.

Hi,

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
http://testbot.winehq.org/JobDetails.pl?Key=1815

Your paranoid android.

=== W98SE (32 bit string) ===
string.c:41: Test failed: Expected 0xdeadbeef, got 0x00000057
string.c:47: Test failed: Expected 0xdeadbeef, got 0x00000057
string.c:53: Test failed: Expected 0xdeadbeef, got 0x00000057
string.c:59: Test failed: Expected 0xdeadbeef, got 0x00000057

[PATCH] kernel32: lstrlen does not call SetLastError.

[Lei Zhang]

On Wed, Apr 28, 2010 at 7:53 PM, Marvin  wrote:
> Hi,
>
> 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
> http://testbot.winehq.org/JobDetails.pl?Key=1815
>
> Your paranoid android.
>
> === W98SE (32 bit string) ===
> string.c:41: Test failed: Expected 0xdeadbeef, got 0x00000057
> string.c:47: Test failed: Expected 0xdeadbeef, got 0x00000057
> string.c:53: Test failed: Expected 0xdeadbeef, got 0x00000057
> string.c:59: Test failed: Expected 0xdeadbeef, got 0x00000057

Thanks Marvin, I guess that explains why the code calls SetLastError.