From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: kevinb@cygnus.com
Cc: ac131313@cygnus.com, Naushit_Sakarvadia@quintum.com,
gdb@sources.redhat.com
Subject: Re: 8 bit read
Date: Tue, 24 Jul 2001 11:11:00 -0000 [thread overview]
Message-ID: <2593-Tue24Jul2001210739+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <1010724162531.ZM20232@ocotillo.lan>
> Date: Tue, 24 Jul 2001 09:25:31 -0700
> From: Kevin Buettner <kevinb@cygnus.com>
> >
> > 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.
>
> Why is this a show stopper?
Because the implementation I had in mind was of a special interactive
command that would accept a selector for a memory region, define a
region, and stick the selector as a special attribute there. The
target-specific memory-transfer function will then see that attribute
when GDB calls the to_xfer_memory method, and use special functions to
access that memory.
But the current API in memattr.c doesn't allow GDB applications code
to create memory regions except via the "mem" commands.
> A sequence of commands which define
> attributes for different memory ranges can be placed in a file and
> then sourced...
I don't see a smiley to go with the joke ;-)
next prev parent reply other threads:[~2001-07-24 11:11 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
2001-07-24 9:25 ` Kevin Buettner
2001-07-24 11:11 ` Eli Zaretskii [this message]
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=2593-Tue24Jul2001210739+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=Naushit_Sakarvadia@quintum.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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