[PATCH] server: Accept DBG_EXCEPTION_HANDLED parameter in continue_debug_event.

[Francois Gouget]

On Fri, 8 Jan 2021, Francois Gouget wrote:
[...]
> So on the 7th we had results for w864, w1064v1507, w1064v1607, 
> w1064v1709, w1064v1809 and w1064 (2009):
[...]
> What survived is the 32-bit w8 VM, and the cw-gtx560 and cw-rx460 non-VM 
> machines (Windows 8 to 10 1809).
> 
> Somehow my Windows 10 VM (fgtb-w10pro64) survived too (kernel 
> 4.19.0-11 (instead of 4.19.0-13) and qemu 5.0-14).

I found a combination that works: kernel 4.19.152-1 (4.19.0-12) + qemu 
5.0.14.

I given that the combinations below don't work I don't think this 
means that the bug is fixed as much as that we're avoiding the error by 
sheer luck.

In the past 24 hours I confirmed that with these kernel + qemu 
combinations, ntdll:exception causes Windows to crash:

kernel 4.19.146-1 (4.19.0-11) + qemu 5.0-14~bpo10+1
kernel 4.19.152-1 (4.19.0-12) + qemu 3.1+dfsg-8+deb10u8
kernel 4.19.160-2 (4.19.0-13) + qemu 3.1+dfsg-8+deb10u8
kernel 4.19.160-2 (4.19.0-13) + qemu 5.0-14~bpo10+1
kernel 5.9.6-1~bpo10+1 (5.9.0-0.bpo.2) + qemu 5.0-14~bpo10+1

So I updated vm3 and vm4 to this configuration but I left vm1 and vm2 
alone for now since they don't have any impacted VM.

-- 
Francois Gouget <fgouget at codeweavers.com>