From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id EDF1F3858C27 for ; Sat, 21 Nov 2020 18:48:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org EDF1F3858C27 Received: from fencepost.gnu.org ([2001:470:142:3::e]:33100) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kgXwQ-0003cB-Eh for gdb@sourceware.org; Sat, 21 Nov 2020 13:48:58 -0500 Received: from pool-96-233-64-159.bstnma.fios.verizon.net ([96.233.64.159]:48170 helo=pdslaptop.home) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kgXwP-0001M8-Cl for gdb@sourceware.org; Sat, 21 Nov 2020 13:48:58 -0500 Message-ID: <3b63c3503a31dabc42315cb133e434c158759a46.camel@gnu.org> Subject: Re: GDB 10.1: Backtrace goes into infinite loop From: Paul Smith Reply-To: psmith@gnu.org To: gdb@sourceware.org Date: Sat, 21 Nov 2020 13:48:56 -0500 In-Reply-To: <5553a2ee-6918-87e6-2283-3cbb37b9ec6f@simark.ca> References: <503bd54a619aa2781d6b1385cbd3db20634addaa.camel@gnu.org> <5553a2ee-6918-87e6-2283-3cbb37b9ec6f@simark.ca> Organization: GNU's Not UNIX! Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.4-0ubuntu1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_PASS, 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: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Nov 2020 18:49:00 -0000 On Sun, 2020-11-15 at 20:04 -0500, Simon Marchi wrote: > When you see the problem happening, you could save a core file (just > run the generate-core-file command). Then, try to reproduce the > problem using the core file. If it reproduces, you could upload it > to a bug report. Hi Simon; thanks for the reply. Just to say that this is still happening and I've now heard from two people on my team who see this behavior. I have not seen it though. I'm asking them to provide me with reproduction core files and binaries. As soon as I have this I will investigate further. Cheers!