From: John Baldwin <jhb@FreeBSD.org>
To: Robert Henry <rrh.henry@gmail.com>, gdb@sourceware.org
Subject: Re: implementation specific registers in elf core files?
Date: Thu, 31 Jan 2019 16:04:00 -0000 [thread overview]
Message-ID: <038eb9c4-13e7-9b1c-aaa1-1c9f5d9311b3@FreeBSD.org> (raw)
In-Reply-To: <CAEYr_8n8XcoNKJzvWYJz9e4miRWKD=enhFgfyDsiPDhAWVf23Q@mail.gmail.com>
On 1/30/19 8:59 PM, Robert Henry wrote:
> I would like to save implementation specific registers in elf core files,
> and have gdb find and print those registers under the guidance of the
> target description machinery (xml reg specs) described in Appendix G. Is
> this possible? I would presume the values would end up in an ELF core file
> note, but what would the note's name and type be, and how does it all come
> together?
You would need to define the note type and format. You would then teach
the note-parsing code in bfd/elf.c to create a pseudosection (look for
elfcore_make_note_pseudosection). You then add register set descriptions in
the gdb/foo-tdep.c file that find the named notes and hook them into the
callback to parse per-thread register notes.
--
John Baldwin
                                                                           Â
prev parent reply other threads:[~2019-01-31 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 4:59 Robert Henry
2019-01-31 16:04 ` John Baldwin [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=038eb9c4-13e7-9b1c-aaa1-1c9f5d9311b3@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=gdb@sourceware.org \
--cc=rrh.henry@gmail.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