This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC/RFA] gdb extension for Harvard architectures
- To: msnyder at cygnus dot com
- Subject: Re: [RFC/RFA] gdb extension for Harvard architectures
- From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
- Date: Sat, 29 Sep 2001 11:26:05 +0200
- CC: gdb-patches at sources dot redhat dot com
- References: <3BB4D843.A92818B9@cygnus.com>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Fri, 28 Sep 2001 13:06:27 -0700
> From: Michael Snyder <msnyder@cygnus.com>
>
> This is an extension to help with debugging on Harvard architectures
> (machines with two or more address spaces, typically one for
> instructions and one for data).
Thanks.
> + /* Instruction-space delimited type. This is for Harvard architectures
> + which have separate instruction and data address spaces (and perhaps
> + others).
> +
> + GDB usually defines a flat address space that is a superset of the
> + architecture's two (or more) address spaces, but this is an extension
> + of the architecture's model.
> +
> + If TYPE_FLAG_INST is set, an object of the corresponding type
> + resides in instruction memory, even if its address (in the extended
> + flat address space) does not reflect this.
> +
> + Similarly, if TYPE_FLAG_DATA is set, then an object of the
> + corresponding type resides in the data memory space, even if
> + this is not indicated by its (flat address space) address.
>
> + If neither flag is set, the default space for functions / methods
> + is instruction space, and for data objects is data memory. */
> +
> + #define TYPE_FLAG_CODE_SPACE (1 << 9)
> + #define TYPE_FLAG_DATA_SPACE (1 << 10)
May I suggest that these new macros be added to the docs
gdbint.texinfo? The large comment tells me they are important enough
to be documented.