From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10595 invoked by alias); 1 Sep 2005 20:10:40 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 10569 invoked by uid 22791); 1 Sep 2005 20:10:33 -0000 Received: from e1.ny.us.ibm.com (HELO e1.ny.us.ibm.com) (32.97.182.141) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 01 Sep 2005 20:10:33 +0000 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e1.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j81KAWSP026117 for ; Thu, 1 Sep 2005 16:10:32 -0400 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay02.pok.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j81KAWMR098208 for ; Thu, 1 Sep 2005 16:10:32 -0400 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.12.11/8.13.3) with ESMTP id j81KAVVQ014496 for ; Thu, 1 Sep 2005 16:10:31 -0400 Received: from austin.ibm.com (netmail2.austin.ibm.com [9.41.248.176]) by d01av01.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j81KAVQ0014457 for ; Thu, 1 Sep 2005 16:10:31 -0400 Received: from lazy.austin.ibm.com (lazy.austin.ibm.com [9.53.94.97]) by austin.ibm.com (8.12.10/8.12.10) with ESMTP id j81KAPtt089624 for ; Thu, 1 Sep 2005 15:10:25 -0500 Date: Thu, 01 Sep 2005 20:10:00 -0000 From: Manoj Iyer X-X-Sender: manjo@lazy To: gdb@sources.redhat.com Subject: infinite loop from backtrace in gdb (Powerpc64) In-Reply-To: <20040421005257.GA11993@nevyn.them.org> Message-ID: References: <4085BE65.3000402@redhat.com> <20040421005257.GA11993@nevyn.them.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2005-09/txt/msg00004.txt.bz2 I am seeing an infinite loop from backtrace in gdb.6.3 on Powerpc64, looks much like the problem Michael tried to fix for MIPS. In my case a library that the app links to calls abort(), the remainder of backtrace from the library seems cause gdb to go into an infinite loop. Any clues? On Tue, 20 Apr 2004, Daniel Jacobowitz wrote: > On Wed, Apr 21, 2004 at 12:20:53AM +0000, Michael Snyder wrote: > > Hi Andrew, > > > > This change will prevent the caller(s) of mips_mdebug_frame_id from > > infinite-looping when we get badly lost on the stack frame. > > > > > 2004-04-21 Michael Snyder > > > > * mips-tdep.c (mips_mdebug_frame_cache): Call error to prevent > > infinite looping by caller. > > (heuristic_proc_start): Warning() already prefixes "Warning: ". > > Since I have some patches to make this "I'm not sure how" case into a > working part of the unwinder, I don't much like this. They got hung up > on the question of how to trust proc_desc's when we might be in the > prologue. > > One time where this case occurs is in backtracing from a NULL pointer > dereference, which happens in the GDB testsuite now. > > > -- > Daniel Jacobowitz > MontaVista Software Debian GNU/Linux Developer >