From: rahul dev <rahul_dev_agg@yahoo.co.in>
To: gdb@sourceware.org
Subject: support for core files for target powerpc-eabi
Date: Sun, 10 Feb 2008 08:48:00 -0000 [thread overview]
Message-ID: <11312.94560.qm@web94605.mail.in2.yahoo.com> (raw)
Guys,
I have configured my gdb for target powerpc-eabi. My host machine is
i686-pc-cygwin.
My aim is to analyze the memory dumps collected from an embedded system.
My embedded system doesn't run any OS. So, I collect the memory dumps
from the system. I then convert these memory dumps to an elf core file.
However, when I try to debug this core file using gdb, I get an error
message "GDB can't read core files on this machine.".
I want to know what is reason for this message? Don't we have a support
to analyze the corefile for powerpc-eabi ?
Now, when I compile gdb for target powerpc-linux, and analyze the same
corefile, I don't get any error message. I can see the contents of
all .data and .bss and other memory sections. I can even see various
registers.
However, the dirty things that I have to do is to construct the
NOTE sections (NT_PRSTATUS) in the same format that powerpc-linux target
does. The gdb has hardcoded the size of prstatus not section for
powerpc-linux to be 268 and looks for GPRs at specific offsets in
pr_reg field of prstatus.
My question is if this is a correct way to do the things ?
Is there a better way of achieve this?
Is there a way to analyze my corefile, if I configure the gdb for
powerpc-eabi, Or should I continue to do configure gdb for powerpc-linux
and construct the NOTE section in the same format linux-powerpc does.
I would be highly grateful for any help/suggestions
thanks a lot in advance.
Get the freedom to save as many mails as you wish. To know how, go to http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html
next reply other threads:[~2008-02-10 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 8:48 rahul dev [this message]
2008-02-10 17:54 ` 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=11312.94560.qm@web94605.mail.in2.yahoo.com \
--to=rahul_dev_agg@yahoo.co.in \
--cc=gdb@sourceware.org \
/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