From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Naushit Sakarvadia <Naushit_Sakarvadia@quintum.com>,
gdb@sources.redhat.com
Subject: Re: 8 bit read
Date: Tue, 24 Jul 2001 04:49:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010724145016.1341T-100000@is> (raw)
In-Reply-To: <3B5C71DA.2090603@cygnus.com>
On Mon, 23 Jul 2001, Andrew Cagney wrote:
> FYI, J.T.C. was working on infrastructure to teach GDB about memory
> attributes. A basic framework is in place only nothing uses it.
> I believe his next step was to extend the protocol so that memory
> packets could include things like the read size.
I think we also need some programmatic interface to define memory
attributes. Right now, the only way to do that is with an interactive
command, because the rest of the interface is private to memattr.c.
I was thinking about using memory attributes to allow GDB access to
segments outside the normal address space of the program being
debugged. This would need some additions to the memory attributes,
but the real show-stopper is that there's no way to define regions and
attributes except interactively.
next prev parent reply other threads:[~2001-07-24 4:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 9:04 Naushit Sakarvadia
2001-07-23 9:56 ` Daniel Jacobowitz
2001-07-23 11:50 ` Andrew Cagney
2001-07-24 4:49 ` Eli Zaretskii [this message]
2001-07-24 9:25 ` Kevin Buettner
2001-07-24 11:11 ` Eli Zaretskii
2001-07-24 14:11 ` Kevin Buettner
2001-07-25 1:45 ` Eli Zaretskii
2001-07-25 11:40 ` Kevin Buettner
2001-07-25 23:39 ` Eli Zaretskii
2001-07-26 6:17 ` Andrew Cagney
2001-07-26 6:45 ` Eli Zaretskii
2001-07-26 6:53 ` Andrew Cagney
2001-07-26 6:59 ` Eli Zaretskii
2001-07-26 7:09 ` Andrew Cagney
2001-07-26 7:01 ` Andrew Cagney
2001-07-26 9:20 ` Kevin Buettner
2001-07-26 9:25 ` 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=Pine.SUN.3.91.1010724145016.1341T-100000@is \
--to=eliz@is.elta.co.il \
--cc=Naushit_Sakarvadia@quintum.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.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