Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] New option "trust-readonly-sections"
Date: Wed, 23 Jan 2002 21:45:00 -0000	[thread overview]
Message-ID: <20020124004435.A11710@nevyn.them.org> (raw)
In-Reply-To: <200201240323.g0O3NI905339@reddwarf.cygnus.com>

On Wed, Jan 23, 2002 at 07:23:18PM -0800, Michael Snyder wrote:
> 
> This is an optimization mainly for remote debugging, or any
> context where reading from the child's memory is expensive.
> 
> In a nutshell, if you trust that read-only sections will really
> not be modified, you can advise GDB of this fact, and GDB will
> then satisfy all memory reads from read-only sections by reading
> from the object file, instead of from the child/target.
> 
> Naturally it defaults to 'off'.
> 
> On targets that do a lot of prologue analysis (which
> involves lots of reads from the text section), this can
> be a huge speed win.
> 
> 2002-01-15  Michael Snyder  <msnyder@redhat.com>
> 
> 	* target.c: New command, "set trust-readonly on".
> 	(do_xfer_memory): Honor the suggestion to trust readonly sections
> 	by reading them from the object file instead of from the target.

<asbestos suit on>

I'd rather see this default to on.  If you give GDB a binary, it's
reasonable that GDB read from it - I though it did in a lot of cases,
but maybe I was mistaken.

If you know it will be modified, then documenting that you must tell
GDB that is reasonable.  IMHO.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2002-01-24  5:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-23 19:29 Michael Snyder
2002-01-23 20:15 ` Andrew Cagney
2002-01-23 21:45 ` Daniel Jacobowitz [this message]
2002-01-23 23:23   ` Eli Zaretskii
2002-01-24  8:35     ` Daniel Jacobowitz
2002-01-24  8:51       ` Andrew Cagney
2002-01-24  9:14         ` Andrew Cagney
2002-01-24  9:25         ` Daniel Jacobowitz
2002-01-23 23:29   ` Stan Shebs
2002-01-24 10:40     ` Michael Snyder
2002-01-24 10:52 ` Andrew Cagney
2002-01-30 18:25   ` Michael Snyder
2002-01-31  1:03     ` Eli Zaretskii

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=20020124004435.A11710@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@cygnus.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