From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27904 invoked by alias); 10 May 2002 19:07:42 -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 27880 invoked from network); 10 May 2002 19:07:41 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 10 May 2002 19:07:41 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D345C3DEC; Fri, 10 May 2002 15:07:49 -0400 (EDT) Message-ID: <3CDC1A85.4090603@cygnus.com> Date: Fri, 10 May 2002 12:07:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0rc1) Gecko/20020429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Richard.Earnshaw@arm.com Cc: gdb@sources.redhat.com Subject: Re: ARM and virtual/raw registers References: <200205101044.LAA25709@cam-mail2.cambridge.arm.com> <3CDBDDDB.5000108@cygnus.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-05/txt/msg00112.txt.bz2 >> Now obviously, in order to do all this correctly the stack-frame groveller will have to record the information as it unwinds the stack in some private data; but creating this information is part of the stack-unwinding process. > > Yes. The arm would need to implement a custom get_saved_register() architecture method. > > Rather than normalize the registers on the way in. Consider normalizing them them on the way out via a pseudo. Doing this would mean that the raw register wouldn't be directly visible and the layer below regcache wouldn't need to normalize anything. [to expand a little] Two target side interfaces (at least) don't have mechanisms for re-aranging (normalizing) registers on the way in: - sim - remote I suspect that at least short term, doing everything on the gdb-core side will be easier. Having the very raw data in the cache may also prove better for debugging - both the raw (in cache) and the normalized (via register read/write) formats are available. Perhaphs also look at the i387 which normalizes things on the way in (and its bug count). enjoy, Andrew