From: Phil Muldoon <pmuldoon@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: frysk@sourceware.org
Subject: Re: Make CoredumpAction use Task.getRegisterBanks()
Date: Fri, 03 Aug 2007 14:18:00 -0000 [thread overview]
Message-ID: <46B33940.6000005@redhat.com> (raw)
In-Reply-To: <1186043315.15044.46.camel@dijkstra.wildebeest.org>
Mark Wielaard wrote:
>
> Thanks. So this seems slightly different from how we do things with
> ptrace/proc where we can have multiple different register banks (for
> floating point, extended floating point and control/debug registers). We
> might be able to always just use the USR address space to get at all of
> those together in one go (I don't actually know why we don't do that, or
> why ptrace provides different ways to access the same register sets).
>
>
Apologies for the delay in replying.
For the FP and fpxregs (which I am writing code for right now), I just
take the entire register buffer and dump it wholesale into the
appropriate note in the core file. For GP registers there are some
cross-isa issues (mainly in PPC) that require the code to pick them
individually, sort them into order, them populate them as part of
another note, the elf_prstatus note. This is an important distinction as
GP registers do not have their own separate note area in core files, but
are part of the thread elf_prstatus note. That is why both raw memory
banks, and getRegisterByName are needed.
> If we can match up the raw memory for each register bank between
> ptrace/proc and core files from Task that would be ideal. Then the Isa
> can just do the getRegisterByName() mapping. I'll watch your rewrite of
> the core file stuff and see if this makes things easier and clearer (I
> guess it will).
>
The two requirements needed for core files are:
1) Access to the raw memory behind the register via a ByteBuffer
2) Access to a logical method of getting registers by name, like
getRegisterByName()
Regards
Phil
next prev parent reply other threads:[~2007-08-03 14:18 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
2007-08-02 8:28 ` Mark Wielaard
2007-08-03 14:18 ` Phil Muldoon [this message]
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=46B33940.6000005@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).