From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5389 invoked by alias); 4 Dec 2003 11:57:02 -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 5379 invoked from network); 4 Dec 2003 11:56:59 -0000 Received: from unknown (HELO web9603.mail.yahoo.com) (216.136.129.182) by sources.redhat.com with SMTP; 4 Dec 2003 11:56:59 -0000 Message-ID: <20031204115658.59820.qmail@web9603.mail.yahoo.com> Received: from [161.114.32.111] by web9603.mail.yahoo.com via HTTP; Thu, 04 Dec 2003 03:56:58 PST Date: Thu, 04 Dec 2003 11:57:00 -0000 From: Marc Paloma Subject: Re: offline core file analysis from a PPC 440GX target on my Solaris hostsystem To: Daniel Jacobowitz Cc: gdb@sources.redhat.com In-Reply-To: <20031204001044.GA18798@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-12/txt/msg00081.txt.bz2 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? 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? -Marc --- Daniel Jacobowitz wrote: > On Wed, Dec 03, 2003 at 04:03:22PM -0800, Marc > Paloma wrote: > > Greetings, > > > > Is it possible to configure a version of GDB for > > "--host=sparc-solaris2.8 and > > --target=powerpc-ibm-vxworks5.5" that can analyze > a > > core file from an IBM PPC 440GX embedded system > > offline? Currently, I'm getting the following > error > > from GDB 5.3: > > > > (gdb) core-file 440gxdump > > GDB can't read core files on this machine. > > > > (1) Is there any version of GDB which is aware of > the > > IBM PPC 440GX processor architecture? I am aware > of > > WindRiver having a version of GDB however, > > their version of GDB does not support the gdb > corefile > > functionality. I'm not interested in remote > online > > debugging of the 440GX. However, I would like a > way > > to build a version of GDB which can analyze a core > > file from a 440GX memory dump and be able to do a > > backtrace, info registers, frame into the stack, > and > > look at local/global variables. > > I do not believe that any PPC VxWorks target > supports core files. You > could try a powerpc-linux debugger but (A) I believe > you'll need 6.0 > and (B) it is unlikely that it will understand the > VxWorks dump notes. > > -- > Daniel Jacobowitz > MontaVista Software Debian > GNU/Linux Developer __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/