|
HI
I have an IOCP server that works (or seems to) when
run normally in both debug and release types. It does throw an exception
when run through the debugger while trying to allocate memory. The call
stack shows only seems to show NTDLL.
The sequence of events leading to the exception are
when a socket is being created for the second time. So it goes something
like
Listen for a Connection
Get hSocket stick it in a list
BindIOCallback with the socket
work with socket
Close socket remove it from list
Then when going around this sort of loop for the
second time (another connection) the sever throws an exception. Has anyone
else come across this??
Regards
Max
|
- Re: [msvc] IOCP Max
- Re: [msvc] IOCP /dev/null
- Re: [msvc] IOCP Max
- RE: [msvc] IOCP Ehsan Akhgari
- Re: [msvc] IOCP Max
- Re: [msvc] IOCP Max
- Re: [msvc] IOCP Max
- Re: [msvc] IOCP Max
- Re: [msvc] IOCP /dev/null
- RE: [msvc] IOCP Ehsan Akhgari
- Re: [msvc] IOCP Max
