[PATCH 2/2] ntdll: Treat INVALID_HANDLE_VALUE as success in CloseHandle.

[Alexandre Julliard]

Daniel Lehman <dlehman(a)esri.com> writes:
> From 11c64857c3b5750a456f7ba54e174b586d5598b8 Mon Sep 17 00:00:00 2001
> From: Daniel Lehman <dlehman(a)esri.com>
> Date: Mon, 14 Mar 2022 12:27:40 -0700
> Subject: [PATCH 2/2] ntdll: Treat INVALID_HANDLE_VALUE as success in
>  CloseHandle.
>
> https://bugs.winehq.org/show_bug.cgi?id=51529
> Signed-off-by: Daniel Lehman <dlehman(a)esri.com>
>
> ---
> visual studio remote debugging hits this exception under wine but not windows
> this change would also fix the above bug
> looks like only windows 10 returns success, and then only on 64-bit

I believe that's meant to catch the GetCurrentProcess() handle, IIRC
there's also GetCurrentThread() and some others that need to be handled
specially.

-- 
Alexandre Julliard
julliard(a)winehq.org

[Daniel Lehman]

> I believe that's meant to catch the GetCurrentProcess() handle, IIRC there's also GetCurrentThread() and some others that need to be handled specially.

Ah, makes sense.  I'll find another way

Thanks
daniel