From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Andreas Tobler <andreast@fgznet.ch>
Subject: Re: mark raw registers the target doesn't have access to as unavailable
Date: Wed, 23 Mar 2011 22:17:00 -0000 [thread overview]
Message-ID: <20110323214421.GJ2520@adacore.com> (raw)
In-Reply-To: <201103232110.52701.pedro@codesourcery.com>
> I think that's overkill: we can just handle this in a centralized
> place, like the patch below. Before the <unavailable> state,
> this was a bit dangerous, because all you would see is a register
> with value 0. Now, it's clearly visible and distinct. Any objection?
None from me, I like it!
--
Joel
next prev parent reply other threads:[~2011-03-23 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 22:14 Pedro Alves
2011-03-23 22:17 ` Joel Brobecker [this message]
2011-03-24 13:38 ` Mark Kettenis
2011-03-24 13:45 ` Pedro Alves
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=20110323214421.GJ2520@adacore.com \
--to=brobecker@adacore.com \
--cc=andreast@fgznet.ch \
--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