|
HI
Right I've fix the first problem. What I was
doing is in the callback I had freed some memory (dropping a connection) but did
not check the pointer which I had then used later on to try and read data off
the network. This didn't crash ( never does when you want it
to ) but it did create a first chance exception. The problem,
really showed itself when I tried to allocate more memory - the debugger showed
that the listening thread memory allocation was going wrong.
Second problem.
I'm getting a first chance exception while getting
the time. Each connection object has a has a function to get the time so I
can see when the last read/write operation tool place and then decide whether to
drop the connection later on or not. Now under certain conditions the
server should drop the connection such as someone logging on with the wrong
ID.
To do this the server send a Error code to the
user and then disconnects - closing the socket, freeing memory etc.
However the Callback gets called again but the Parameters hold information
that's not valid.
Regards
Max
|
- [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
- RE: [msvc] IOCP Ehsan Akhgari
- Re: [msvc] IOCP Max
- Re: [msvc] IOCP /dev/null
