X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7EAF5395B41A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1618370461;
	bh=RT5q8oLCD+976MclPfKedtXGp8JNBqDvedWB7/6VV1U=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=LPlawOy2wJs2Uy5ZauwbIBDG02ETRUj44nOYVwSJGxmS63vlA8lsgoczC3OmhvGMb
	 9nQ2AxhdpRmMSa00jxqukfXOWcjTUKrkDL+/1J4H+SiswRuJIS34VPNpxQAMs/DoEC
	 K52tIhE/c0/qoAV35F+eP1xMHhmYRIGx3IShB7kY=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 08BA8395ACC9
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com 13E3Ke7k003760
X-Nifty-SrcIP: [124.155.50.190]
Date: Wed, 14 Apr 2021 12:20:50 +0900
To: cygwin AT cygwin DOT com
Subject: Re: cgdb fails with cygwin 3.2.0 but is OK with 3.1.6
Message-Id: <20210414122050.635aad4fb1582b7e55c242f2@nifty.ne.jp>
In-Reply-To: <90c72430-8eb6-8132-0728-0afe20e48a0c@gmail.com>
References: <alpine DOT WNT DOT 2 DOT 00 DOT 2104131455150 DOT 56864 AT panamint>
 <alpine DOT WNT DOT 2 DOT 00 DOT 2104131951470 DOT 93188 AT panamint>
 <90c72430-8eb6-8132-0728-0afe20e48a0c AT gmail DOT com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-3.7 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT, NICE_REPLY_A,
 RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Content-Type: text/plain; charset="utf-8"
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 13E3L4rg022255

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 DOT yano AT nifty DOT ne DOT jp>
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple