From: Michael Snyder <msnyder@redhat.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Don't use deprecated regcache functions
Date: Thu, 13 Apr 2006 18:58:00 -0000 [thread overview]
Message-ID: <443E9F48.4030308@redhat.com> (raw)
In-Reply-To: <20060412.210543.123363581.davem@davemloft.net>
David S. Miller wrote:
> From: Michael Snyder <msnyder@redhat.com>
> Date: Wed, 12 Apr 2006 19:41:42 -0700
>
>
>>I get confused just thinking about all these variants.
>>If you have an argument for why one is more correct in
>>this context, I'm certainly open to it. I can't really
>>convince myself that the current behavior is correct,
>>since deprecated_read_register_gen calls regcache_cooked_read,
>>which may call regcache_raw_read, which may call
>>target_fetch_registers *before* capturing the current value.
>>Which it seems like would defeat the purpose of the whole
>>exercise...
>
>
> Any of these arguments for or against apply to the Solaris thread code
> which does use regcache_raw_read() in this same exact situation.
>
Oh, I see -- you did mention that you were emulating
that code, but I didn't read thoroughly -- I thought
you were only referring to the fetch_registers call.
Well, I'm gonna plead ignorance, then. I don't know enough
to say whether the change is correct or not.
Daniel? Mark?
next prev parent reply other threads:[~2006-04-13 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 8:39 David S. Miller
2006-04-11 13:01 ` Daniel Jacobowitz
2006-04-11 21:13 ` David S. Miller
2006-04-12 19:25 ` Michael Snyder
2006-04-13 1:09 ` David S. Miller
2006-04-13 2:41 ` Michael Snyder
2006-04-13 4:05 ` David S. Miller
2006-04-13 18:58 ` Michael Snyder [this message]
2006-04-20 17:02 ` Daniel Jacobowitz
2006-05-05 22:43 ` David S. 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=443E9F48.4030308@redhat.com \
--to=msnyder@redhat.com \
--cc=davem@davemloft.net \
--cc=gdb-patches@sources.redhat.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