X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4A2AF39518B4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1618340176; bh=9TkkPJJ1LXVNPLMAZ1TLxQClwvMYGuSvgA6JuwsOp/c=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=ZMnYON72ZbtPhDLKbAg+sRYL+7IVPKJ+3UNggIBGL8EXaMbb18sM1sf3mElc4FXF3 mpG5AQoKGXXR9KiYoUCcuFHvjuYCK6cMsSKoFC4Jv21RjYSmxnJm/WcLK7ZVCM6Bhv xB7R7/0bQXdF4zqAtGfUTpAT3ksJbi8ZYVpHdiuk= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 20CFC3949D80 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus Date: Tue, 13 Apr 2021 19:56:07 +0100 (GMT Summer Time) To: cygwin AT cygwin DOT com Subject: Re: cgdb fails with cygwin 3.2.0 but is OK with 3.1.6 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (WNT 1167 2008-08-23) X-X-Sender: acn1 AT imap DOT hermes DOT cam DOT ac DOT uk MIME-Version: 1.0 Content-ID: X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00, DKIMWL_WL_MED, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, 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-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: cygwin AT cygwin DOT 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: , From: Arthur Norman via Cygwin Reply-To: Arthur Norman Cc: =?ISO-8859-15?Q?Ren=E9_Berber?= Content-Type: text/plain; charset="iso-8859-15"; Format="flowed" Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id 13DIuJ2U017297 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! Arthur -- 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