Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Jacob Potter <jdpotter@google.com>,  gdb-patches@sourceware.org
Subject: Re: [RFA] Rewrite data cache and use for stack access.
Date: Mon, 29 Jun 2009 19:58:00 -0000	[thread overview]
Message-ID: <4A491C7B.5060306@vmware.com> (raw)
In-Reply-To: <20090629193230.GA8840@caradoc.them.org>

Daniel Jacobowitz wrote:

> The other especially useful place is code analysis.  If code accesses
> were marked appropriately, we could redirect them straight to the
> executable (mild risk, see my recent conversation with Pedro about
> fix-and-continue style patching) or to the data cache (almost no
> risk).  

By the way, we can already redirect them to the executable
by using "set trust-readonly-sections".


  reply	other threads:[~2009-06-29 19:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 19:01 Jacob Potter
2009-06-29 19:32 ` Daniel Jacobowitz
2009-06-29 19:58   ` Michael Snyder [this message]
2009-06-29 20:03     ` Daniel Jacobowitz
2009-06-30 21:16   ` Jacob Potter
2009-06-30 21:28     ` Daniel Jacobowitz

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=4A491C7B.5060306@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jdpotter@google.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