From: rahul dev <rahul_dev_agg@yahoo.co.in>
To: gdb@sourceware.org
Subject: Re: elf core file format for powerpc
Date: Tue, 05 Feb 2008 19:45:00 -0000 [thread overview]
Message-ID: <19374.94556.qm@web94614.mail.in2.yahoo.com> (raw)
In-Reply-To: <8f2776cb0802051131s2d8e866cu3c06984a4dba9743@mail.gmail.com>
--- On Wed, 6/2/08, Jim Blandy <jimb@red-bean.com> wrote:
> From: Jim Blandy <jimb@red-bean.com>
> Subject: Re: elf core file format for powerpc
> To: rahul_dev_agg@yahoo.co.in
> Cc: gdb@sourceware.org
> Date: Wednesday, 6 February, 2008, 1:01 AM
> On Feb 5, 2008 5:42 AM, rahul dev
> <rahul_dev_agg@yahoo.co.in> wrote:
> > Can you please provide some information on the note
> section and how to
> > add register values in the note section. I searched a
> lot on the net
> > but failed to get any useful information.
>
> One source of confusion is that the code in GDB that
> operates on BFD
> sections is actually accessing ELF notes, in a PT_NOTE
> program header.
> When BFD opens a core file and sees a PT_NOTE program
> header, it
> turns each note into a "section" with a known
> name. See
> bfd/elfcore.h:elf_core_file_p, and uses of
> _bfd_elfcore_make_pseudosection.
>
> So if you want to produce .reg "sections" that
> GDB can see, you need
> to produce PT_NOTE program headers in your core that BFD
> will
> recognize.
Thanks Jim. I can read the registers from the core file now.
Also, readelf was really useful, specially the -n option.
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
prev parent reply other threads:[~2008-02-05 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 13:07 rahul dev
2008-02-05 13:19 ` Daniel Jacobowitz
2008-02-05 13:26 ` rahul dev
2008-02-05 13:31 ` Daniel Jacobowitz
2008-02-05 13:43 ` rahul dev
2008-02-05 19:32 ` Jim Blandy
2008-02-05 19:37 ` Jim Blandy
2008-02-05 19:45 ` rahul dev [this message]
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=19374.94556.qm@web94614.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