A new attempt on WSACleanup

[Matt Durgavich]

Why are we looking at the dll side again? 

-Matt

> On Sep 9, 2015, at 9:47 AM, Henri Verbeet <hverbeet at gmail.com> wrote:
> 
> On 9 September 2015 at 06:31, Bruno Jesus <00cpxxx at gmail.com> wrote:
>> Hi all, a possible way to solve the WSACleanup in the DLL side is to
>> retrieve all existing sockets from the current process in a server
>> call and then closing then inside winsock. Is it possible to make a
>> wine server call that returns variable length data? If yes, can anyone
>> show an example?
>> 
> Yes, see the various requests with VARARG() replies. In ws2_32 in
> particular there's _get_sock_errors(), although that uses a fixed
> buffer. In ntdll there's e.g. server_get_unix_name().
> 
>