From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23775 invoked by alias); 3 Jun 2003 02:33:54 -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 23652 invoked from network); 3 Jun 2003 02:33:50 -0000 Received: from unknown (HELO localhost.redhat.com) (24.157.166.107) by sources.redhat.com with SMTP; 3 Jun 2003 02:33:50 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 2BC0B2B2F; Mon, 2 Jun 2003 22:33:29 -0400 (EDT) Message-ID: <3EDC08F9.10809@redhat.com> Date: Tue, 03 Jun 2003 02:33:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: [patch rfc] Add frame memory & arch methods References: <3EDBF301.2050001@redhat.com> <20030603012300.GB1150@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-06/txt/msg00113.txt.bz2 > On Mon, Jun 02, 2003 at 08:59:45PM -0400, Andrew Cagney wrote: > >> Hello, >> >> This adds per-frame memory and architecture methods. Instead of using >> the global variablecurrent_gdbarch and the context dependant >> read_memory, architecture code can use these. Should help future proof >> architecture code should thread/target changes start happening. >> >> It uses them in the d10v. >> >> I'll commit in a few days. > > > Could you explain to us where you see this going? Right now it looks > like a solution without a problem. Sure, someday they may need a > target parameter, but until we're closer to that day I don't see why a > frame parameter is the way to go. Ref: [multi-arch] The frame as the global parameter (long, important), http://sources.redhat.com/ml/gdb/2001-02/msg00335.html Andrew