Newsgroups : Borland : borland.public.delphi.internet.winsock : 2007 Nov : Re: Input Buffer empty
| Subject: | Re: Input Buffer empty |
| Posted by: | "Remy Lebeau (TeamB)" (no.spam@no.spam.com) |
| Date: | Wed, 5 Dec 2007 19:02:51 |
"Larry Killen" <lkillen@charter.net> wrote in message
news:4757473b@newsgroups.borland.com...
> Here is the call stack leading up to the exception....
<snip>
> and then the raised exception
The *only* way InputBufferIsEmpty() can raise an exception is if it is
called on an invalid IOHandler object. So either your thread's FConn member
is not valid to begin with, or its IOHandler was freed while the thread is
still running.
> AND THAT IS EXACTLY WHAT I AM SEEING!!
But you still haven't said what actual exception type is being thrown, or
what its message actually says.
> TIdIOHandler.CheckForDataOnSource(0) <= Call stack
TIdIOHandler.WaitFor() does not call CheckForDataOnSource() with a timeout
of 0 milliseconds.
Gambit