From: Marc Paloma <marc_paloma@yahoo.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: offline core file analysis from a PPC 440GX target on my Solaris hostsystem
Date: Thu, 04 Dec 2003 11:57:00 -0000 [thread overview]
Message-ID: <20031204115658.59820.qmail@web9603.mail.yahoo.com> (raw)
In-Reply-To: <20031204001044.GA18798@nevyn.them.org>
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 <drow@mvista.com> 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/
next prev parent reply other threads:[~2003-12-04 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 0:03 Marc Paloma
2003-12-04 0:10 ` Daniel Jacobowitz
2003-12-04 11:57 ` Marc Paloma [this message]
2003-12-04 13:30 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031204115658.59820.qmail@web9603.mail.yahoo.com \
--to=marc_paloma@yahoo.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox