From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2860 invoked by alias); 4 Dec 2003 13:30:09 -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 2850 invoked from network); 4 Dec 2003 13:30:06 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 4 Dec 2003 13:30:06 -0000 Received: from drow by nevyn.them.org with local (Exim 4.24 #1 (Debian)) id 1ARtYR-0000w4-5p; Thu, 04 Dec 2003 08:30:03 -0500 Date: Thu, 04 Dec 2003 13:30:00 -0000 From: Daniel Jacobowitz To: Marc Paloma Cc: gdb@sources.redhat.com Subject: Re: offline core file analysis from a PPC 440GX target on my Solaris hostsystem Message-ID: <20031204133002.GA3550@nevyn.them.org> Mail-Followup-To: Marc Paloma , gdb@sources.redhat.com References: <20031204001044.GA18798@nevyn.them.org> <20031204115658.59820.qmail@web9603.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031204115658.59820.qmail@web9603.mail.yahoo.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-12/txt/msg00082.txt.bz2 On Thu, Dec 04, 2003 at 03:56:58AM -0800, Marc Paloma wrote: > Daniel, > > If I compile a version of GDB 6.0 with > --host=sparc-solaris2.8 and --target=powerpc-sun-elf, > what kind of PowerPC processor support will I get? Is > 440GX included among the PowerPC processors that is > supported by GDB 6.0? GDB does not usually care at all what specific processor is targeted. I believe all of the 440GX's instructions will be disassembled more-or-less correctly. > In terms of the core file, is it possible to create an > ELF core image to represent the memory regions > belonging to the 440GX process image? This core image > will be writing to a filesystem which then can be > ftp'ed to a UNIX environment where I can use GDB to > analyze the dump. I'm hoping that I can reconstruct > the executable from the core dump using the actual ELF > binary application and the ELF core dump. Once the > core is loaded into GDB, I'm hoping that GDB will be > able to figure out the stack and disassemble the > opcodes. How does GDB figure out stack information of > a a.out core dump? Are the dump notes that you were > refering to correlate to the text and data sections? I can only suggest you investigate the format of ELF core files, in bfd and GDB, and compare it to what VxWorks gives you. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer