From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6587 invoked by alias); 13 Jan 2003 21:42:11 -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 6540 invoked from network); 13 Jan 2003 21:42:08 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by 209.249.29.67 with SMTP; 13 Jan 2003 21:42:08 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 0FC653C63; Mon, 13 Jan 2003 16:41:58 -0500 (EST) Message-ID: <3E2332A5.10403@redhat.com> Date: Mon, 13 Jan 2003 21:42:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.1) Gecko/20021211 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Warkentin Cc: Elena Zannoni , Fernando Nasser , Felix Lee , gdb@sources.redhat.com Subject: Re: patch to use target specific .gdbinit file References: <200301102242.h0AMgTl02921@paper-wolf-solo.tigerfood.org> <0d6601c2bb1e$70a94670$0202040a@catdog> <3E230B07.8030607@redhat.com> <0e5301c2bb36$1002c400$0202040a@catdog> <3E2315B5.8030003@redhat.com> <0e8401c2bb47$c00d89a0$0202040a@catdog> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg00212.txt.bz2 >> > Here's a question: does a multi-targetted gdb know what it's targetting > > at > >> > the point of reading the .gdbinit or is this determined later? Is it >> > switchable per session? I'm thinking that another possibility is to > > have it > >> > check for .gdbinit-$TARGET at the time that the target is determined. > >> >> To clarify something here, target and architecture are separate but very >> related. GDB configured for a certain TARGET, will support one or more >> architectures. The x86-64, for instance, also supports i386. >> >> For a normal GDB session, an architecture will be selected twice. Once >> for the default, and once based on the file that is loaded. The second >> selection may occure before, during or after, .gdbinit parsing. The >> `target' however, won't change. > > > So, to clarify further, a single gdb binary can only support a single target > but multiple architectures? A single gdb executable can support multiple `target architectures'. Those architectures, as with i386 / x86-64 are not necessarily of the same family. A single gdb executable can support multiple `target interfaces'. For instance, remote, pmon, and ptrace. A single gdb executable's configuration options (target interfaces, target architectures, initial architecture, ....) are selected by the --target=TARGET option (and in the future --enable-targets=...). > If this is the case then your method of > enabling this at config time would be just fine. I was thinking of a (for > instance) ppc/x86 gdb but I didn't think that was possible which was what I > wanted to ask. Er, that is a single gdb executable supporting ``multiple architectures''. Andrew