ntdll/tests: Use inline implementation of NtCurrentTeb for exception tests.

[Sebastian Lackner]

On 13.07.2016 09:50, 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
> https://testbot.winehq.org/JobDetails.pl?Key=24168
> 
> Your paranoid android.
> 
> 
> === wvistau64 (32 bit exception) ===
> exception.c:489: Test failed: 42: Unexpected eip 0x3d0000/0x3d0001
> exception: unhandled exception 80000004 at 003D0000
> exception.c:489: Test failed: 42: Unexpected eip 0x77baed97/0x3d0001
> 
> === w7u (32 bit exception) ===
> exception.c:489: Test failed: 42: Unexpected eip 0x280000/0x280001
> exception: unhandled exception 80000004 at 00280000
> exception.c:489: Test failed: 42: Unexpected eip 0x77cde34f/0x280001
> 
> === w1064 (32 bit exception) ===
> An error occurred while waiting for the test to complete: network read timed out (wait2/connect:AgentVersion.h:0/9)
> The test VM has crashed, rebooted or lost connectivity (or the TestAgent server died)
> 
> === w1064 (64 bit exception) ===
> An error occurred while waiting for the test to complete: network read timed out (wait2/connect:AgentVersion.h:0/9)
> The test VM has crashed, rebooted or lost connectivity (or the TestAgent server died)
> 

These failures were already existing before and are unrelated to this patch.