I am sitting here at a break point right now with the exception, "Input
Buffer Empty" on my screen. The order of events are exactly as stated. If
I could send you a capture, I would capture teh call stack and send it to
you.
There is nothing more I can show you. The next call stack message is
:7c90378b ntdll.RtlConvertUlongToLargeInteger + 0x46. Double clicking it
takes me into the CPU view. Ther there is the NotifyNonDelphiException and
the kernel32RaiseException.
That is all.
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:4757661d$1@newsgroups.borland.com...
>
> "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
