This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

offline core file analysis from a PPC 440GX target on my Solaris hostsystem


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.

(2) If I create a separate ELF formatted file of my
embedded application (to read in the symbols) and a
separate corefile of when the application halted
(corefile), could I analyze the dump file offline
using GDB on my Solaris workstation (i.e. not
connected to the 440GX processor). If so, how would I
configure the --target settings (i.e.
--target=powerpc-???-???) and what other code
modifications must I endure in order to get this to
work.

I'm new to GDB debugging and corefile analysis so I
apoligize if more clarification on my part is
necessary.  Andrew Cagney recommended I send my
inquires here so any help or insight would be very
much appreciated.

-Marc Paloma



__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]