From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19638 invoked by alias); 27 Jun 2002 03:26:55 -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 19629 invoked from network); 27 Jun 2002 03:26:54 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 27 Jun 2002 03:26:54 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 9E0943C44; Wed, 26 Jun 2002 23:26:44 -0400 (EDT) Message-ID: <3D1A85F4.9000706@ges.redhat.com> Date: Wed, 26 Jun 2002 20:26:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020613 X-Accept-Language: en-us, en MIME-Version: 1.0 To: davidm@hpl.hp.com Cc: gdb-patches@sources.redhat.com, davidm@napali.hpl.hp.com Subject: Re: new gdb arch routine FRAME_UNCHANGED References: <200205110023.g4B0NVCF004832@napali.hpl.hp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-06/txt/msg00550.txt.bz2 > The patch below defines a new gdbarch routine called FRAME_UNCHANGED. > This is needed for gdb/ia64 because the ia64 architecture has two > separate stack pointers (one for memory stack and one for register stack). > Because of the two stacks, it's not possible to look just at the frame > pointer and PC to determine whether a frame changed. > > If the patch looks OK, I'd appreciate if someone could apply it. > > Note: the patch below doesn't include the ia64 version of > FRAME_UNCHANGED. It is part of a larger update to add unwind library > support to gdb/ia64 and I'll submit that separately. So, for now, the > patch is effectively a no-op for all platforms. > > Also, it will be necessary to re-generate gdbarch.[ch] after applying > the patch. Just to follow this up. The frame_id code has been committed. I think this has the potential of affecting the way you did your patch. For instance, it could compare frame_id's for either sameness or more inner_than. Andrew