Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [rfa] Restore "trust-readonly-section"
Date: Sun, 15 May 2005 17:25:00 -0000	[thread overview]
Message-ID: <20050515171254.GC11855@nevyn.them.org> (raw)
In-Reply-To: <00e201c55748$533cea10$aaa56b80@msnyder8600>

On Thu, May 12, 2005 at 04:14:19PM -0700, Michael Snyder wrote:
> Hmm, tabs fubar -- I'll try again with the patch as an attachment.
> 
> ----- Original Message ----- 
> From: "Michael Snyder" <msnyder@redhat.com>
> To: "GDB Patches" <gdb-patches@sources.redhat.com>
> Sent: Thursday, May 12, 2005 3:55 PM
> Subject: [rfa] Restore "trust-readonly-section"
> 
> 
> >This seems to have succumbed to bit-rot -- there are new target-read 
> >functions
> >in target.c that don't pay any attention to this user-settable mode bit.
> >
> >The purpose of "trust-readonly-sections" is to improve speed on
> >targets where reading memory is expensive (mostly remote).
> >It checks to see if a read is from a read-only section, and if so,
> >reads it from the exec file.  It defaults to "off" for safety, but if
> >users choose to use it, it really speeds up prologue analysis
> >(and therefore stepping).
> >
> >This patch just makes it work again.

It seems odd to add the test both in target_xfer_partial (a dispatcher)
and default_xfer_partial (an implementation).  Are they really both
necessary?

The code might be simpler if you push the trust_readonly check inside
target_read_trusted.  Also, could you name that something involving
memory?

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-05-15 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13  6:29 Michael Snyder
2005-05-13 11:41 ` Michael Snyder
2005-05-15 17:25   ` Daniel Jacobowitz [this message]
2005-05-24  2:03     ` Michael Snyder
2005-05-28 22:55       ` Daniel Jacobowitz
2005-06-11 15:26       ` Mark Kettenis

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=20050515171254.GC11855@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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