Lines Matching full:mapped
5800 the memory region. Often memory mapped device registers require
5822 about volatile variables or memory mapped device registers.
6915 mapped by asking the inferior.
6954 mapped --->+-----------+ | | +-----------+
6971 address space. Since the overlays shown here all use the same mapped
6972 address, only one may be mapped at a time. For a system with a single
6978 called a "mapped" overlay; its "mapped address" is its address in the
6981 address in the larger memory. The mapped address is also called the
6991 program must make sure that overlay is actually mapped.
7002 not its mapped address. However, each overlay's instructions must
7004 mapped address. You can use GNU linker scripts to specify
7019 overlay's load area contents simply appear at their mapped address
7021 the overlay to its mapped area in the usual way.
7024 one overlay area, and have more than one overlay mapped at a time.
7033 mapped area.
7045 mapped and load addresses. Identifying overlays with sections allows
7047 depending on whether the overlay is mapped or not.
7055 their mapped addresses. By default, GDB's overlay support is
7060 you to tell it which overlays are mapped, and which are not, using
7066 Tell GDB that OVERLAY is now mapped; OVERLAY must be the name of
7068 is mapped, GDB assumes it can find the overlay's functions and
7069 variables at their mapped addresses. GDB assumes that any other
7070 overlays whose mapped ranges overlap that of OVERLAY are now
7075 Tell GDB that OVERLAY is no longer mapped; OVERLAY must be the
7083 see which overlays are mapped. For details, see *Note Automatic
7096 Display a list of the overlays currently mapped, along with their
7097 mapped addresses, load addresses, and sizes.
7111 No sections are mapped.
7114 When `foo''s overlay is mapped, GDB prints the function's name
7119 mapped at 0x1016 - 0x104a
7125 is mapped. This allows most GDB commands, like `break' and
7134 your overlay manager (and tell GDB which overlays are now mapped,
7144 GDB can automatically track which overlays are mapped and which are
7159 /* The overlay's mapped address. */
7168 /* Non-zero if the overlay is currently mapped;
7170 unsigned long mapped;
7178 To decide whether a particular overlay is mapped or not, GDB looks
7181 finds a matching entry, it consults the entry's `mapped' member to
7182 determine whether the overlay is currently mapped.
7200 at their load addresses, while relocating them to run at their mapped
9860 file whose image is mapped directly into the inferior's memory.
11304 memory range includes the object file which is mapped to that
11411 mapped into physical addresses. A Page Table includes an entry
11412 for every page of memory that is mapped into the program's address
19278 they had been mapped to `self-insert'. The default is `off'.
20486 source for the GNU memory-mapped malloc package
21244 packet may not be suitable for accessing memory-mapped I/O devices.
26115 * listing mapped overlays: Overlay Commands. (line 60)
26224 * mapped address: How Overlays Work. (line 6)
26225 * mapped overlays: How Overlays Work. (line 6)
