From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-04.nifty.com (conssluserg-04.nifty.com [210.131.2.83]) by sourceware.org (Postfix) with ESMTPS id B6DA53848016 for ; Tue, 27 Apr 2021 19:14:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B6DA53848016 Received: from Express5800-S70 (v050190.dynamic.ppp.asahi-net.or.jp [124.155.50.190]) (authenticated) by conssluserg-04.nifty.com with ESMTP id 13RJERDI010826; Wed, 28 Apr 2021 04:14:27 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-04.nifty.com 13RJERDI010826 X-Nifty-SrcIP: [124.155.50.190] Date: Wed, 28 Apr 2021 04:14:30 +0900 From: Takashi Yano To: cygwin@cygwin.com Subject: Re: gdb under emacs is now aborting Message-Id: <20210428041430.134a16f9a64e996ecbfba434@nifty.ne.jp> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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: Tue, 27 Apr 2021 19:15:02 -0000 On Tue, 27 Apr 2021 09:58:01 -0400 "William M. \(Mike\) Miller via Cygwin" wrote: > I refreshed my Cygwin installation over the weekend, and ever since I have > not been able to run gdb under emacs as I previously had done. I use M-x > gdb to start the gud interface, and as soon as I enter the "run" command, I > get a message saying either "Debugger aborted (core dumped)" or a similar > message reporting a segmentation violation in the debugger. I have tried > various combinations of previous versions of emacs and gdb, but all have > the same result. gdb run from a regular shell window works fine. I assume, > then, that it's something else in my environment that changed with the > refresh last weekend. I don't recall when my most recent previous refresh > of the Cygwin installation was, but it's probably on the order of a couple > or three months, so whatever the problem is, it might not be > terribly recent. > > Thanks for any suggestions. Could you please try latest snapshot? https://cygwin.com/snapshots/ -- Takashi Yano