From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: Re: [GOLDSTAR] Re: gdb pty problem [Was: emacs gud-interface is not updated after gdb command execution (maybe because of incomplete output from gdb)]
Date: Thu, 02 Jun 2016 02:09:00 -0000 [thread overview]
Message-ID: <695vkbdlgrb1qr4o4suk1f96se55nija8d@4ax.com> (raw)
In-Reply-To: <20160601210522.GA21837@calimero.vinschen.de>
> On Jun 1 16:01, Ken Brown wrote:
> > On 6/1/2016 3:54 PM, Corinna Vinschen wrote:
> > > On Jun 1 15:05, Ken Brown wrote:
> > > > On 6/1/2016 2:28 PM, Corinna Vinschen wrote:
> > > > > On Jun 1 11:22, Ken Brown wrote:
> > > > > > And this also fixes the original problem in emacs that started the thread:
> > > > > >
> > > > > > https://www.cygwin.com/ml/cygwin/2016-05/msg00318.html
> > > > >
> > > > > 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
> > > > (http://www.fruitbat.org/Cygwin/#cygwintimemachine). The bisection I did,
> > > > spanning a period of about 4 years, would have been virtually impossible
> > > > without it.
> > >
> > > Huh. I was thinking of git bisect. It's incredibly helpful. But, yes,
> > > all power to the Cygwin time machine :)
> >
> > I first used the time machine to narrow down the problem to between 1.7.35
> > and 2.0.0. Then I used git bisect to finish the job. But even for that I
> > needed the time machine; for example, I needed an old version of the w32api
> > headers in order to build an old cygwin1.dll.
>
> Wow, thanks for going to such great lengths to track down the
> regression. Andrew, do we have a GOLDSTAR for Ken here? He really
> deserves it.
Shiny! http://cygwin.com/goldstars/#KB
--
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
next prev parent reply other threads:[~2016-06-02 2:09 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
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 [this message]
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=695vkbdlgrb1qr4o4suk1f96se55nija8d@4ax.com \
--to=schulman.andrew@epa.gov \
--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).