Am running a chat system using tcp for data transfer but I have a problem
am unable to fix and was wondering if anyone else had this issue.
basically when using my app for more then 3 days it would cash but not a
full socket crash were it would boot people it would just stop accepting
new inco
Am running a chat system using tcp for data transfer but I have a problem am
unable to fix and was wondering if anyone else had this issue.
basically when using my app for more then 3 days it would cash but not a full
socket crash were it would boot people it would just stop accepting new
incom
While testing, I also had during some time FD_READ triggered but
ReceiveFrom returning -1.
Isn't that quite common, if those are WSAEWOULDBLOCK errors?
As far as I know, not so much. I saw is returning -1 during 4 seconds which
is the timeout time in my appication.
--
francois.pie...@overby
Francois PIETTE wrote:
>>> GDisplayProc is assigned a routine which output the message to the
>>> console window and to the log file and which is used all over the
>>> application.
>>>
>>> Guess what ? It works !
>>> This is not satisfying since the log file is full of unwanted
>>> messages and th
GDisplayProc is assigned a routine which output the message to the
console window and to the log file and which is used all over the
application.
Guess what ? It works !
This is not satisfying since the log file is full of unwanted
messages and this probably only hides the real problem.
Does th
Surely, an attached debugger is going to use some CPU time, however
small even if nothing triggers it, therefore, the debugged program cycle
timing will change somehow, however small.
Plus, however the debugger works, it could be forcing some other process
(in the kernel) to do it's job more often
