From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-03.nifty.com (conssluserg-03.nifty.com [210.131.2.82]) by sourceware.org (Postfix) with ESMTPS id 08BA8395ACC9 for ; Wed, 14 Apr 2021 03:20:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 08BA8395ACC9 Received: from Express5800-S70 (v050190.dynamic.ppp.asahi-net.or.jp [124.155.50.190]) (authenticated) by conssluserg-03.nifty.com with ESMTP id 13E3Ke7k003760 for ; Wed, 14 Apr 2021 12:20:40 +0900 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 From: Takashi Yano To: cygwin@cygwin.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: <90c72430-8eb6-8132-0728-0afe20e48a0c@gmail.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Apr 2021 03:21:00 -0000 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