From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23192 invoked by alias); 11 Apr 2002 01:58:48 -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 23126 invoked from network); 11 Apr 2002 01:58:45 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 11 Apr 2002 01:58:45 -0000 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 16vTqy-0001i9-00; Wed, 10 Apr 2002 21:58:24 -0400 Date: Wed, 10 Apr 2002 18:58:00 -0000 From: Daniel Jacobowitz To: Jason R Thorpe , gdb@sources.redhat.com Subject: Re: cross-debugging of userland core files, nat -> tdep Message-ID: <20020410215824.A6539@nevyn.them.org> Mail-Followup-To: Jason R Thorpe , gdb@sources.redhat.com References: <20020410183918.C22095@dr-evil.shagadelic.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020410183918.C22095@dr-evil.shagadelic.org> User-Agent: Mutt/1.3.23i X-SW-Source: 2002-04/txt/msg00164.txt.bz2 On Wed, Apr 10, 2002 at 06:39:18PM -0700, Jason R Thorpe wrote: > Hi folks... > > I've been thinking of what needs to happen in order to support > cross-debugging of userland core files in NetBSD. > > BFD can already handle NetBSD ELF core files in the appropriate way. As > far as I can tell, the only stumbling block is getting GDB to play nicely > with them. > > The problem is that the functions that supply registers, etc. from the core > file are all in "nat" modules. This is probably mostly an artifact of the > data being in the same format as the reg structure returned by ptrace(2). > > What I'd like to do is move those supply-registers routines into an > appropriate "tdep" file. They can still be used by the "nat" routines > which use ptrace(2), and all the core file handling goo can then go into > the "tdep" module, as well. > > If this sounds reasonable, then I'll start my little project. Otherwise, > I'd love to hear suggestions :-) Hit the nail on the head. I believe I've gotten BFD to understand ELF core files appropriately for a fair number of targets; you may need to add a platform-specific chunk to all the ones I didn't get to. Then move supply_* out of the nat files, and link in the core code. Now, if you've got time, there's a much better way to do this. The "magic" supply_* and fetch_* names need to go; we should instead have a table of regset types, sizes, and fetch/supply functions. I just haven't gotten around to actually doing that. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer