From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19735 invoked by alias); 4 Sep 2003 22:07:20 -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 19691 invoked from network); 4 Sep 2003 22:07:18 -0000 Received: from unknown (HELO walton.kettenis.dyndns.org) (213.93.115.144) by sources.redhat.com with SMTP; 4 Sep 2003 22:07:18 -0000 Received: from elgar.kettenis.dyndns.org (elgar.kettenis.dyndns.org [192.168.0.2]) by walton.kettenis.dyndns.org (8.12.6p2/8.12.5) with ESMTP id h84M75dG008337; Fri, 5 Sep 2003 00:07:05 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (localhost [127.0.0.1]) by elgar.kettenis.dyndns.org (8.12.6p2/8.12.6) with ESMTP id h84M75WQ034349; Fri, 5 Sep 2003 00:07:05 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: (from kettenis@localhost) by elgar.kettenis.dyndns.org (8.12.6p2/8.12.6/Submit) id h84M759T034346; Fri, 5 Sep 2003 00:07:05 +0200 (CEST) Date: Thu, 04 Sep 2003 22:07:00 -0000 Message-Id: <200309042207.h84M759T034346@elgar.kettenis.dyndns.org> From: Mark Kettenis To: drow@mvista.com CC: ac131313@redhat.com, gdb@sources.redhat.com In-reply-to: <20030904151338.GA5328@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 4 Sep 2003 11:13:39 -0400) Subject: Re: [RFC] Register sets References: <200308232249.h7NMnvhh090154@elgar.kettenis.dyndns.org> <20030824164347.GA17520@nevyn.them.org> <200308252234.h7PMYqFu001245@elgar.kettenis.dyndns.org> <3F4B8173.1000302@redhat.com> <20030826165547.GA22836@nevyn.them.org> <86he3xrkjb.fsf@elgar.kettenis.dyndns.org> <20030904125514.GA2577@nevyn.them.org> <3F574587.70401@redhat.com> <20030904140822.GA22838@nevyn.them.org> <3F575472.2030405@redhat.com> <20030904151338.GA5328@nevyn.them.org> X-SW-Source: 2003-09/txt/msg00067.txt.bz2 Date: Thu, 4 Sep 2003 11:13:39 -0400 From: Daniel Jacobowitz > >>As for the architecture, supply_regset needs this. It might, for > >>instance, be an x86-64 method supplying registers to an i386 register > >>cache. > > > > > >It needs the regcache's architecture, but I don't believe it needs any > >other. The method will be defined for a particular regcache layout, > >which incorporates all of the information it needs about the other > >involved architecture. We could get the regcache's architecture from > >the regcache, or pass it explicitly. > > That's the architecture mark was passing in. The alternative is a > larger table of regcache X regset maps. No, Mark was passing in the core's architecture != the regcache's architecture. Indeed I was, and it's the wrong thing to do. Mark