From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31263 invoked by alias); 27 Oct 2003 15:21:55 -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 31255 invoked from network); 27 Oct 2003 15:21:54 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 27 Oct 2003 15:21:54 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 59DE32B89; Mon, 27 Oct 2003 10:21:54 -0500 (EST) Message-ID: <3F9D3812.2090801@redhat.com> Date: Mon, 27 Oct 2003 15:21:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Jon Ringle , gdb@sources.redhat.com Subject: Re: Infinite backtrace on arm References: <200310260028.13745.jon.ringle@comdial.com> <20031027145320.GA26422@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00286.txt.bz2 > The problem is that there's not much GDB can do with hand-coded > assembly functions. > > However, GDB ought to be able to detect and stop that loop without any > of this. It seems to me that the problem is not two frames with the > same PC, but two frames with their PC "saved" in the same place - i.e. > GDB failing to figure out where the PC is saved. This is made a little > tricky in current versions of GDB, because the PC is normally unwound > using frame_pc_unwind (which doesn't tell us where it was saved, since > the interface doesn't assume it's a single normal register), and the > core code doesn't have a concept of a "PC register" any more. > > Andrew, any idea on how to do this? Before anything else, find out what a current GDB does - its code to detect a "corrupt stack" is now much improved. Andrew