From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: cgdb fails with cygwin 3.2.0 but is OK with 3.1.6
Date: Wed, 14 Apr 2021 12:20:50 +0900 [thread overview]
Message-ID: <20210414122050.635aad4fb1582b7e55c242f2@nifty.ne.jp> (raw)
In-Reply-To: <90c72430-8eb6-8132-0728-0afe20e48a0c@gmail.com>
On Tue, 13 Apr 2021 14:13:57 -0500
René Berber wrote:
> On 4/13/2021 1:56 PM, Arthur Norman via Cygwin wrote:
> > René Berber wrote
> >> At one time it was recommended to disable a Cygwin feature, something
> >> like this:
> >> alias cgdb="env CYGWIN=disable_pcon cgdb"
> >> Not sure if this is still necesary.
> >
> > Thank you for the reminder about that. I had forgotten - however ion my
> > main Windows machine I have the CYGWIN variable set like that all the
> > time and in the VM that I tried with it is not - and in both cases cgdb
> > seems to behave well on the slightly old version of the cygwin package
> > but failed with the latest. So I do not think that is the issue here and
> > I might live advice as to whether I can now remove that setting of CYGWIN!
>
> Probably. And since you don't see any difference then that's proof that
> is no longer needed (in this case).
In cygwin 3.2.0, pseudo console is automatically disabled
in cgdb regardless of setting CYGWIN=disable_pcon. Therefore,
it is not necessary any more.
Thanks.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2021-04-14 3:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 14:05 Arthur Norman
2021-04-13 17:55 ` René Berber
2021-04-13 18:56 ` Arthur Norman
2021-04-13 19:13 ` René Berber
2021-04-14 3:20 ` Takashi Yano [this message]
2021-04-14 3:13 ` Takashi Yano
2021-04-14 7:28 ` Arthur Norman
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=20210414122050.635aad4fb1582b7e55c242f2@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).