From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8156 invoked by alias); 7 Aug 2003 06:08:17 -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 8145 invoked from network); 7 Aug 2003 06:08:15 -0000 Received: from unknown (HELO lisa.goe.net) (134.76.166.209) by sources.redhat.com with SMTP; 7 Aug 2003 06:08:15 -0000 Received: from mutter.goe.net (mutter-lisa0.a11.local [192.168.31.26]) by lisa.goe.net (8.12.6/8.12.6) with ESMTP id h7768D8i027311; Thu, 7 Aug 2003 08:08:13 +0200 Received: from whitebox.a11.local ([192.168.31.90] helo=whitebox.as.local) by mutter.goe.net with esmtp (Exim 4.20) id 19kdwb-0004Bb-9n; Thu, 07 Aug 2003 08:08:13 +0200 Received: from whitebox.as.local (localhost [127.0.0.1]) by whitebox.as.local (8.12.7/8.12.7/SuSE Linux 0.6) with ESMTP id h7768CsZ006554; Thu, 7 Aug 2003 08:08:12 +0200 Received: (from andreas@localhost) by whitebox.as.local (8.12.7/8.12.7/Submit) id h7768Bt3006553; Thu, 7 Aug 2003 08:08:11 +0200 X-Authentication-Warning: whitebox.as.local: andreas set sender to schwab@suse.de using -f To: Josef Wolf Cc: gdb@sources.redhat.com Subject: Re: Need Help for bringing m68k-based bdm target-patches form gdb-5.2.1 to gdb-5.3 References: <20030731223514.GD20282@raven.inka.de> <20030806205431.GA3349@raven.inka.de> From: Andreas Schwab X-Yow: Yow! Now we can become alcoholics! Date: Thu, 07 Aug 2003 06:08:00 -0000 In-Reply-To: <20030806205431.GA3349@raven.inka.de> (Josef Wolf's message of "Wed, 6 Aug 2003 22:54:31 +0200") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-08/txt/msg00087.txt.bz2 Josef Wolf writes: > Ough? Does that mean that gdb should not be used to debug supervisor mode? GDB was designed to debug user level programs, which have no way to see supervisor-only registers. So from GDB's point of view they don't exist. That does not mean that GDB on m68k can not be extended to handle them, you just need a way to get their contents from the target (no current m68k target provides that). >> Theses numbers are basically arbitrary, AFAIK. > > But there are places like By arbitrary I mean not externally imposed. The numbers are chosen for convenience inside GDB, and exposed only to the target interface, where they are suitably translated when communicating with the target. > BTW: I still don't have a clue what this MULTI_ARCH stuff is all about and > how multi-arch targets are meant to be adopted. MULTI_ARCH means that every target architecture hooks in through the gdbarch structure at runtime, instead of hard coding the interface characteristics at compile time. Targets that set GDB_MULTI_ARCH to GDB_MULTI_ARCH_PARTIAL are not quite there yet, but the basic support is present. Andreas.