aboutsummaryrefslogtreecommitdiff
path: root/gdb/xcoffsolib.h
diff options
context:
space:
mode:
Diffstat (limited to 'gdb/xcoffsolib.h')
-rw-r--r--gdb/xcoffsolib.h33
1 files changed, 33 insertions, 0 deletions
diff --git a/gdb/xcoffsolib.h b/gdb/xcoffsolib.h
new file mode 100644
index 0000000..9e5e4ef
--- /dev/null
+++ b/gdb/xcoffsolib.h
@@ -0,0 +1,33 @@
+/*
+ the vmap struct is used to describe the virtual address space of
+ the target we are manipulating. The first entry is always the "exec"
+ file. Subsequent entries correspond to other objects that are
+ mapped into the address space of a process created from the "exec" file.
+ These are either in response to exec()ing the file, in which case all
+ shared libraries are loaded, or a "load" system call, followed by the
+ user's issuance of a "load" command. */
+
+struct vmap {
+ struct vmap *nxt; /* ^ to next in chain */
+ bfd *bfd; /* BFD for mappable object library */
+ char *name; /* ^ to object file name */
+ char *member; /* ^ to member name */
+ CORE_ADDR tstart; /* virtual addr where member is mapped */
+ CORE_ADDR tend; /* virtual upper bound of member */
+ CORE_ADDR tadj; /* heuristically derived adjustment */
+ CORE_ADDR dstart; /* virtual address of data start */
+ CORE_ADDR dend; /* vitrual address of data end */
+
+ CORE_ADDR ostart; /* objext start ??? */
+ unsigned loaded:1; /* True if symbols are loaded */
+ unsigned reloced:1; /* True, if symbols relocated */
+ unsigned padding:14;
+};
+
+
+struct vmap_and_bfd {
+ bfd *pbfd;
+ struct vmap *pvmap;
+};
+
+extern struct vmap *vmap;