From: David Miller <davem@davemloft.net>
To: pedro@codesourcery.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix regcache_restore() handling of unavailable regs.
Date: Tue, 11 Oct 2011 18:28:00 -0000 [thread overview]
Message-ID: <20111011.142815.759252421999066508.davem@davemloft.net> (raw)
In-Reply-To: <201110111144.49959.pedro@codesourcery.com>
From: Pedro Alves <pedro@codesourcery.com>
Date: Tue, 11 Oct 2011 11:44:49 +0100
> OOC, what register are you seeing as unavailable?
%wim and %tbr on sparc 32-bit
> Is this a case of ptrace not exposing all the machine's registers?
Yes, ptrace() does not provide these registers. They really aren't
relevant for analyzing userland process execution at all.
They are, however, useful when debugging an operating system over
a serial line with GDB, and the Sparc infrastructure for that does
properly provide these registers.
next prev parent reply other threads:[~2011-10-11 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 6:40 David Miller
2011-10-11 10:45 ` Pedro Alves
2011-10-11 18:28 ` David Miller [this message]
2011-10-11 10:50 ` Pedro Alves
2011-10-11 18:28 ` David Miller
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=20111011.142815.759252421999066508.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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