From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] MI: lvalues and variable_editable
Date: Fri, 02 Nov 2007 11:36:00 -0000 [thread overview]
Message-ID: <20071102113610.GA16883@caradoc.them.org> (raw)
In-Reply-To: <18218.42464.899738.594153@kahikatea.snap.net.nz>
On Fri, Nov 02, 2007 at 05:21:52PM +1300, Nick Roberts wrote:
> In that case for such a varobj, var->value == NULL must indicate that the
> memory was inaccessible at the _last_ update, or creation, and it may no longer
> be inaccessible. Describing it as "noneditable" may then be a bit misleading.
The next time it's -var-update'd it may get a new value; presumably
the IDE does that periodically.
> I'm surprised that there is "no way to be sure without trying to write". I
> know that 0x0 is inaccessible memory, and presumably the OS has a better idea
> about what is and isn't accessible.
It won't tell us, though. Most systems have no interface to ask this
question. Unix ptrace doesn't, hardware JTAG doesn't... whether you
can always write to RAM from a hardware JTAG device depends on whether
you're going through the MMU (memory management unit) or not for
writes.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-11-02 11:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 22:59 Nick Roberts
2007-10-27 6:29 ` Vladimir Prus
2007-10-27 12:15 ` Nick Roberts
2007-10-27 14:22 ` Vladimir Prus
2007-10-30 8:55 ` Nick Roberts
2007-10-30 9:55 ` Vladimir Prus
2007-10-30 11:15 ` Nick Roberts
2007-10-30 13:41 ` Daniel Jacobowitz
2007-10-30 18:30 ` Nick Roberts
2007-10-30 19:26 ` Daniel Jacobowitz
2007-10-30 19:27 ` Daniel Jacobowitz
2007-11-01 4:42 ` Nick Roberts
2007-10-31 14:16 ` Vladimir Prus
2007-11-01 4:52 ` Nick Roberts
2007-11-01 7:52 ` Vladimir Prus
2007-11-01 15:40 ` Daniel Jacobowitz
2007-11-02 4:23 ` Nick Roberts
2007-11-02 11:36 ` Daniel Jacobowitz [this message]
2007-11-03 9:23 ` Nick Roberts
2007-11-03 9:48 ` Vladimir Prus
2007-11-03 23:14 ` Nick Roberts
2007-11-20 13:39 ` Vladimir Prus
2007-11-03 11:09 ` Nick Roberts
2007-11-20 13:55 ` Daniel Jacobowitz
2007-11-20 19:55 ` Nick Roberts
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=20071102113610.GA16883@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=nickrob@snap.net.nz \
/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