From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Emacs gud not working on new installation
Date: Thu, 05 Mar 2020 13:05:00 -0000 [thread overview]
Message-ID: <20200305194018.b286ababefc9dae8f22d3c98@nifty.ne.jp> (raw)
In-Reply-To: <CAH5rLZV0Q+OkS7jzDe9pCA8Av59AKmH41zpj1TMoXMwhQ+EVcw@mail.gmail.com>
On Wed, 4 Mar 2020 10:39:11 -0500
"William M. (Mike) Miller" wrote:
> On Wed, Mar 4, 2020 at 9:58 AM Ken Brown wrote:
>
> > On 3/4/2020 9:44 AM, William M. (Mike) Miller wrote:
> > > I installed Cygwin on a new computer last weekend. On my previous
> > computer,
> > > I used gud with gdb in emacs (M-x gdb) for debugging. However, on the new
> > > computer it is not working. I suspect that gdb is producing output that
> > is
> > > not formatted correctly for gud to parse.
>
> [...snip...]
>
> >
> > I don't know whether this is an emacs problem or a Cygwin problem. Here
> > are two things you can try:
> >
> > 1. Roll back the cygwin package to 3.0.7 to see if that fixes the
> > problem. If so, the problem is likely related to the pty changes in
> > cygwin-3.1.x.
> >
>
> This worked. Thanks for the tip!
I guess starting emacs with:
CYGWIN=disable_pcon emacs
helps in cygwin 3.1.4.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
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:[~2020-03-05 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 15:39 William M. (Mike) Miller
2020-03-04 15:59 ` Ken Brown
2020-03-04 18:16 ` William M. (Mike) Miller
2020-03-05 13:05 ` Takashi Yano [this message]
2020-03-05 14:27 ` William M. (Mike) Miller
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=20200305194018.b286ababefc9dae8f22d3c98@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).