From: Andrew Cagney <ac131313@redhat.com>
To: "Liang, James" <jliang@sandia.gov>
Cc: "'insight@sources.redhat.com'" <insight@sources.redhat.com>
Subject: Re: xfer_memory instead of target_read_memory in gdbtk_dis_asm_read_m emory
Date: Mon, 05 May 2003 21:09:00 -0000 [thread overview]
Message-ID: <3EB6D322.1040304@redhat.com> (raw)
In-Reply-To: <71251C7D5FB1D2119C8F0008C7A44ED10379207F@es07snlnt.sandia.gov>
> Why is it that
> gdbtk_dis_asm_read_memory uses xfer_memory instead of target_read_memory??
> I see the documented assumption, but why is that
> assumption made?
Performance. Accessing the local executable's text section is faster
than a remote target's memory.
However, the assumption has problems. Insight can't disassemble stuff
in the BSS section or on the stack.
GDB's gdb_disassemble() function was recent changed to not do this
performance tweak, instead ``set trust read-only-sections on'' can be
used. Insight should also just use gdb_disassemble().
Andrew
prev parent reply other threads:[~2003-05-05 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 19:12 Liang, James
2003-05-05 21:09 ` Andrew Cagney [this message]
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=3EB6D322.1040304@redhat.com \
--to=ac131313@redhat.com \
--cc=insight@sources.redhat.com \
--cc=jliang@sandia.gov \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).