From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30435 invoked by alias); 11 Apr 2002 01:39:33 -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 30360 invoked from network); 11 Apr 2002 01:39:19 -0000 Received: from unknown (HELO dr-evil.shagadelic.org) (208.176.2.162) by sources.redhat.com with SMTP; 11 Apr 2002 01:39:19 -0000 Received: by dr-evil.shagadelic.org (Postfix, from userid 7518) id A1CB49869; Wed, 10 Apr 2002 18:39:18 -0700 (PDT) Date: Wed, 10 Apr 2002 18:39:00 -0000 From: Jason R Thorpe To: gdb@sources.redhat.com Subject: cross-debugging of userland core files, nat -> tdep Message-ID: <20020410183918.C22095@dr-evil.shagadelic.org> Reply-To: thorpej@wasabisystems.com Mail-Followup-To: Jason R Thorpe , gdb@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Wasabi Systems, Inc. X-SW-Source: 2002-04/txt/msg00163.txt.bz2 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 :-) Thanks. -- -- Jason R. Thorpe