This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gdb pty problem [Was: emacs gud-interface is not updated after gdb command execution (maybe because of incomplete output from gdb)]

On 6/1/2016 2:28 PM, Corinna Vinschen wrote:
On Jun  1 11:22, Ken Brown wrote:
On 6/1/2016 10:33 AM, Ken Brown wrote:
On 6/1/2016 10:28 AM, Corinna Vinschen wrote:
Hi Ken,

On Jun  1 09:02, Ken Brown wrote:
On 6/1/2016 8:51 AM, Ken Brown wrote:
On 5/31/2016 5:41 AM, Corinna Vinschen wrote:
Any chance you could bisect Cygwin to help finding the culprit?

The culprit is

commit 252a07b0ad3353abcd0fcd9b1b65ff977acd679e
Author: Takashi Yano <>
Date:   Fri Apr 3 13:07:35 2015 +0900

   Cygwin hangs up if several keys are typed during outputting a lot of

       * (fhandler_pty_slave::read): Change
calculation of
       "readlen" not to use "bytes_in_pipe" value directly.

Reverting that commit fixes the problem.

Unfortunately, all kinds of other things break.  For example, emacs
immediately, ls produces no output,....

Are you sure?  I just tried it myself and ls as well as emacs work
fine for me.

It works for me now too.  I must have done something wrong the first
time I tried.

And this also fixes the original problem in emacs that started the thread:

I reverted commit 252a07b0ad3353abcd0fcd9b1b65ff977acd679e in git master
for now, unless we find a reason to rework this again.

Thanks. By the way, I'd like to take the opportunity to thank Peter Castro for the Cygwin Time Machine ( The bisection I did, spanning a period of about 4 years, would have been virtually impossible without it.


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]