This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: 8 bit read
- To: kevinb at cygnus dot com
- Subject: Re: 8 bit read
- From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
- Date: Tue, 24 Jul 2001 21:07:39 +0300
- CC: ac131313 at cygnus dot com, Naushit_Sakarvadia at quintum dot com, gdb at sources dot redhat dot com
- References: <Pine.SUN.3.91.1010724145016.1341T-100000@is> <1010724162531.ZM20232@ocotillo.lan>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> 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 ;-)