From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22688 invoked by alias); 11 Dec 2005 22:34:17 -0000 Received: (qmail 22679 invoked by uid 22791); 11 Dec 2005 22:34:16 -0000 X-Spam-Check-By: sourceware.org Received: from yosemite.airs.com (HELO yosemite.airs.com) (205.217.158.180) by sourceware.org (qpsmtpd/0.31) with SMTP; Sun, 11 Dec 2005 22:34:14 +0000 Received: (qmail 4250 invoked from network); 11 Dec 2005 22:26:16 -0000 Received: from zproxy.gmail.com (64.233.162.201) by yosemite.airs.com with SMTP; 11 Dec 2005 22:26:16 -0000 Received: by zproxy.gmail.com with SMTP id f1so1231095nzc for ; Sun, 11 Dec 2005 14:06:15 -0800 (PST) Received: by 10.36.20.6 with SMTP id 6mr5430567nzt; Sun, 11 Dec 2005 13:56:15 -0800 (PST) Received: by 10.37.2.6 with HTTP; Sun, 11 Dec 2005 13:56:14 -0800 (PST) Message-ID: <8f2776cb0512111356q6e2b08bs63635dedfc1fbf3d@mail.gmail.com> Date: Sun, 11 Dec 2005 22:34:00 -0000 From: Jim Blandy To: Kim Lux Subject: Re: How is info.bfd_arch_info set ? Cc: gdb@sourceware.org In-Reply-To: <1134332830.14961.19.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1134332391.14961.10.camel@localhost.localdomain> <1134332830.14961.19.camel@localhost.localdomain> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-12/txt/msg00139.txt.bz2 You need to tell us more about what you're doing. There's no global variable called 'info', so you must be looking at a local variable of some function; which function? How did you get there? The m68hc11_gdbarch_init function will usually be called more than once. If I remember right, once for GDB's default architecture and once for the architecture it gets from the executable file. So don't assume that, because it's being called once with the wrong bfd_arch_info structure, that that's the one it will actually use.=20 After you've told GDB which executable file you want it to use for debugging information, use 'show arch' to see what architecture it's using.