Re: IOCP touching my OVERLAPPED after my Write has completed
- From: "Code Jockey" <gimme@xxxxxxxxxxxx>
- Date: Fri, 18 Aug 2006 14:43:22 -0700
"m" <m@xxx> wrote in message news:%23QxURvwwGHA.4972@xxxxxxxxxxxxxxxxxxxxxxx
The short answer is that when the call to GQCS returns the buffers
(OVERLAPPED & data) can be freed immediately.
Alberto: re-examine AllocateRequest(), because it seems that it is returning
a pointer to memory that was already allocated and already sent down to
Winsock, and then sent down again in another request. This would explain
why it is touched by Winsock again. This is pure conjecture.
.
- References:
- Re: IOCP touching my OVERLAPPED after my Write has completed
- From: anton bassov
- Re: IOCP touching my OVERLAPPED after my Write has completed
- From: anton bassov
- Re: IOCP touching my OVERLAPPED after my Write has completed
- From: Alberto Demichelis
- Re: IOCP touching my OVERLAPPED after my Write has completed
- From: m
- Re: IOCP touching my OVERLAPPED after my Write has completed
- From: Alberto Demichelis
- Re: IOCP touching my OVERLAPPED after my Write has completed
- From: m
- Re: IOCP touching my OVERLAPPED after my Write has completed
- Prev by Date: Re: Application crashes when a function is called
- Next by Date: Role of the code segment register during "far" CALLs
- Previous by thread: Re: IOCP touching my OVERLAPPED after my Write has completed
- Next by thread: Re: IOCP touching my OVERLAPPED after my Write has completed
- Index(es):
Loading