Request for help debugging screen problem

Christopher Faylor
Fri Feb 5 15:00:00 GMT 2010

On Fri, Feb 05, 2010 at 03:51:54PM +0100, Corinna Vinschen wrote:
>On Feb  5 09:35, Christopher Faylor wrote:
>> On Fri, Feb 05, 2010 at 02:46:48PM +0100, Corinna Vinschen wrote:
>> >On Feb  5 10:42, Shaddy Baddah wrote:
>> >> before and after the ReadFile the error code can return a different
>> >> value. ie. a call to the following function, returns different
>> >> values:
>> >> 
>> >> ssize_t client_request::error_code() const;
>> >> 
>> >> I'm curious as to how this could be. Is there some callback function
>> >> registered via the Windows API that ReadFile calls at various points
>> >> in its execution? Or is another thread setting this value?
>> >> 
>> >> Any help would be greatly appreciated.
>> >
>> >Can yopu expolain this in more detail, please?  What error codes
>> >are returned, and how do you trigger the effect?
>> Also, unless you have CYGWIN=server set, this code should not be used
>> by the pty handler so I don't know why you're looking here.
>Beep.  CYGWIN=server doesn't exist anymore.  But, of course, it still
>requires a running cygserver.

Ah, right.  So, I have never debugged the tty handling in cygserver.  Is
this the root cause of some of the screen error reports?


More information about the Cygwin-developers mailing list