[PATCH v2] ntdll: Add exception handling around DbgBreakPoint.

[Akihiro Sagawa]

On Mon, 30 Sep 2019 12:59:24 -0500, Marvin wrote:
> Hi,
> 
> While running your changed tests, 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=57152
> 
> Your paranoid android.
> 
> 
> === w7u (32 bit report) ===
> 
> kernel32:
> debugger.c:1427: Test failed: unexpected instruction pointer 77986074
> 
> === w1064v1809 (64 bit report) ===
> 
> kernel32:
> debugger.c:1427: Test failed: unexpected instruction pointer 00007FFC9194F844
> 
> === debian10 (32 bit report) ===
> 
> kernel32:
> debugger.c:320: Test failed: GetThreadContext failed: 5
> 
> === debian10 (32 bit Chinese:China report) ===
> 
> kernel32:
> debugger.c:320: Test failed: GetThreadContext failed: 5
> debugger.c:320: Test failed: GetThreadContext failed: 5
> debugger.c:320: Test failed: GetThreadContext failed: 5
> debugger.c:320: Test failed: GetThreadContext failed: 5
> 
> === debian10 (32 bit WoW report) ===
> 
> kernel32:
> debugger.c:320: Test failed: GetThreadContext failed: 5
> debugger.c:320: Test failed: GetThreadContext failed: 5
> debugger.c:320: Test failed: GetThreadContext failed: 5
> debugger.c:320: Test failed: GetThreadContext failed: 5
> debugger.c:320: Test failed: GetThreadContext failed: 5
> 
> === debian10 (64 bit WoW report) ===
> 
> kernel32:
> debugger.c:320: Test failed: GetThreadContext failed: 5

These test failures aren't related to my patch.
When I posted the same patch before [1], they aren't detected.

[1]
https://testbot.winehq.org/JobDetails.pl?Key=57100

Akihiro Sagawa