public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: gdb pty problem [Was: emacs gud-interface is not updated after gdb command execution (maybe because of incomplete output from gdb)]
Date: Wed, 01 Jun 2016 14:33:00 -0000	[thread overview]
Message-ID: <aad3bfc2-c6a5-3299-2e66-90892286753b@cornell.edu> (raw)
In-Reply-To: <20160601142804.GG11431@calimero.vinschen.de>

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 <takashi.yano@nifty.ne.jp>
>>> Date:   Fri Apr 3 13:07:35 2015 +0900
>>>
>>>    Cygwin hangs up if several keys are typed during outputting a lot of
>>> texts.
>>>
>>>        * fhandler_tty.cc (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 exits
>> 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.

Thanks for rechecking.

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2016-06-01 14:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26 12:32 emacs gud-interface is not updated after gdb command execution (maybe because of incomplete output from gdb) Tobias Zawada
2016-05-26 15:48 ` William M. (Mike) Miller
2016-05-26 17:48 ` Ken Brown
2016-05-26 18:00   ` Tobias Zawada
2016-05-26 18:01     ` Ken Brown
2016-05-31  1:47   ` gdb pty problem [Was: emacs gud-interface is not updated after gdb command execution (maybe because of incomplete output from gdb)] Ken Brown
2016-05-31  9:35     ` Ken Brown
2016-05-31 22:41       ` Corinna Vinschen
2016-06-01 12:51         ` Ken Brown
2016-06-01 13:02           ` Ken Brown
2016-06-01 14:28             ` Corinna Vinschen
2016-06-01 14:29               ` Corinna Vinschen
2016-06-01 14:33               ` Ken Brown [this message]
2016-06-01 15:22                 ` Ken Brown
2016-06-01 18:29                   ` Corinna Vinschen
2016-06-01 19:05                     ` Ken Brown
2016-06-01 19:54                       ` Corinna Vinschen
2016-06-01 20:01                         ` Ken Brown
2016-06-01 21:05                           ` [GOLDSTAR] " Corinna Vinschen
2016-06-02  2:09                             ` Andrew Schulman
2016-06-01 14:18           ` Corinna Vinschen
2016-06-06 10:12             ` Takashi Yano
2016-06-06 13:16               ` Corinna Vinschen
2016-06-07 13:14                 ` Takashi Yano
2016-06-07 16:11                   ` Corinna Vinschen
2016-06-06 14:01               ` Ken Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aad3bfc2-c6a5-3299-2e66-90892286753b@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).