From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8659 invoked by alias); 2 Apr 2004 23:01:45 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 8649 invoked from network); 2 Apr 2004 23:01:42 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 2 Apr 2004 23:01:42 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i32N1fjl022734 for ; Fri, 2 Apr 2004 18:01:41 -0500 Received: from localhost.redhat.com (to-dhcp51.toronto.redhat.com [172.16.14.151]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i32N1fj21861; Fri, 2 Apr 2004 18:01:41 -0500 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 7F1752B92; Fri, 2 Apr 2004 18:01:43 -0500 (EST) Message-ID: <406DF0D7.5060704@gnu.org> Date: Fri, 02 Apr 2004 23:01:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Joel Brobecker Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA] Fix an unwinding problem on alpha-tru64 References: <20040401003449.GY888@gnat.com> In-Reply-To: <20040401003449.GY888@gnat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-04/txt/msg00083.txt.bz2 Applied and committed, trunk and branch. > Index: alpha-tdep.c > =================================================================== > RCS file: /cvs/src/src/gdb/alpha-tdep.c,v > retrieving revision 1.128 > diff -u -p -r1.128 alpha-tdep.c > --- alpha-tdep.c 23 Mar 2004 14:47:54 -0000 1.128 > +++ alpha-tdep.c 31 Mar 2004 23:58:36 -0000 > @@ -1029,6 +1029,16 @@ alpha_heuristic_frame_unwind_cache (stru > { > reg = (word & 0x03e00000) >> 21; > > + /* Ignore this instruction if we have already encountered > + an instruction saving the same register earlier in the > + function code. The current instruction does not tell > + us where the original value upon function entry is saved. > + All it says is that the function we are scanning reused > + that register for some computation of its own, and is now > + saving its result. */ > + if (info->saved_regs[reg]) > + continue; > + > if (reg == 31) > continue; > Andrew