From: Phil Muldoon <pmuldoon@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: frysk@sourceware.org
Subject: Re: Make CoredumpAction use Task.getRegisterBanks()
Date: Wed, 01 Aug 2007 00:27:00 -0000 [thread overview]
Message-ID: <46AFD351.6030004@redhat.com> (raw)
In-Reply-To: <1185883408.3653.106.camel@dijkstra.wildebeest.org>
Mark Wielaard wrote:
>
> For ptrace/proc based Tasks there are basically 4 register banks (not
> all of them used on all architectures) the Isa provides a mapping from
> the actual register names to the bank and offset inside it. The four
> banks are the regular registers (gotten through PTRACE_GETREGS), the
> general floating point registers (gotten through PTRACE_GETFPREGS), the
> extended floating point registers such like sse xmm registers (gotten
> through PTRACE_getXFPREGS) and the other registers (gotten through the
> start of USR memory space) that cover things like debug control
> registers found by the Isa through the mapping in sys/user.h (some of
> the other register banks are actually also contained in this one).
>
> Does this map somewhat to how core files handle the register banks, so
> you can just dump/read these banks from them?
>
Pretty much other than General Purpose registers which needs to be
accessed independently via getRegisterByName(). The the rest are just
dumped wholesale into the notes, and in that instance accessed via
task.getRegisterBanks().
I think, going forward access to the raw memory for each register bank,
and also a getRegisterByName() function (which is the functionality we
have now) is needed, and probably will be down the line.
Regards
Phil
next prev parent reply other threads:[~2007-08-01 0:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 16:53 Mark Wielaard
2007-07-30 17:44 ` Phil Muldoon
2007-07-31 12:03 ` Mark Wielaard
2007-08-01 0:27 ` Phil Muldoon [this message]
2007-08-02 8:28 ` Mark Wielaard
2007-08-03 14:18 ` Phil Muldoon
2007-08-06 10:03 ` Mark Wielaard
2007-08-22 21:33 ` Phil Muldoon
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=46AFD351.6030004@redhat.com \
--to=pmuldoon@redhat.com \
--cc=frysk@sourceware.org \
--cc=mark@klomp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).