From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-32071-listarch-gdb-patches=sources.redhat.com@sources.redhat.com>
Received: (qmail 28984 invoked by alias); 2 Apr 2004 23:45:20 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 28942 invoked from network); 2 Apr 2004 23:45:17 -0000
Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108)
  by sources.redhat.com with SMTP; 2 Apr 2004 23:45:17 -0000
Received: by takamaka.act-europe.fr (Postfix, from userid 507)
	id 8379447D62; Fri,  2 Apr 2004 15:45:11 -0800 (PST)
Date: Fri, 02 Apr 2004 23:45:00 -0000
From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix an unwinding problem on alpha-tru64
Message-ID: <20040402234511.GD871@gnat.com>
References: <20040401003449.GY888@gnat.com> <406DF0D7.5060704@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <406DF0D7.5060704@gnu.org>
User-Agent: Mutt/1.4i
X-SW-Source: 2004-04/txt/msg00086.txt.bz2

> Applied and committed, trunk and branch.

Thank you.

> >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;

-- 
Joel