/* Definitions for symbol file management in GDB.
- Copyright (C) 1992 Free Software Foundation, Inc.
+ Copyright (C) 1992, 1993, 1994 Free Software Foundation, Inc.
This file is part of GDB.
/* This structure maintains information on a per-objfile basis about the
"entry point" of the objfile, and the scope within which the entry point
exists. It is possible that gdb will see more than one objfile that is
- executable, each with it's own entry point.
+ executable, each with its own entry point.
For example, for dynamically linked executables in SVR4, the dynamic linker
code is contained within the shared C library, which is actually executable
CORE_ADDR entry_point;
+#define INVALID_ENTRY_POINT (~0) /* ~0 will not be in any file, we hope. */
+
/* Start (inclusive) and end (exclusive) of function containing the
entry point. */
CORE_ADDR main_func_lowpc;
CORE_ADDR main_func_highpc;
-};
+/* Use these values when any of the above ranges is invalid. */
+/* We use these values because it guarantees that there is no number that is
+ both >= LOWPC && < HIGHPC. It is also highly unlikely that 3 is a valid
+ module or function start address (as opposed to 0). */
+
+#define INVALID_ENTRY_LOWPC (3)
+#define INVALID_ENTRY_HIGHPC (1)
+
+};
/* Sections in an objfile.
addresses", but that's not true; addr & endaddr are actual memory
addresses. */
CORE_ADDR offset;
-
- sec_ptr sec_ptr; /* BFD section pointer */
- /* Objfile this section is part of. Not currently used, but I'm sure
- that someone will want the bfd that the sec_ptr goes with or something
- like that before long. */
+ sec_ptr the_bfd_section; /* BFD section pointer */
+
+ /* Objfile this section is part of. */
struct objfile *objfile;
};
struct obj_section
*sections,
*sections_end;
+
+ /* two auxiliary fields, used to hold the fp of separate symbol files */
+ FILE *auxf1, *auxf2;
};
/* Defines for the objfile flag word. */
/* Gdb can arrange to allocate storage for all objects related to a
- particular objfile in a designated section of it's address space,
+ particular objfile in a designated section of its address space,
managed at a low level by mmap() and using a special version of
malloc that handles malloc/free/realloc on top of the mmap() interface.
This allows the "internal gdb state" for a particular objfile to be
#define OBJF_SYMS (1 << 1) /* Have tried to read symbols */
+/* When an object file has its functions reordered (currently Irix-5.2
+ shared libraries exhibit this behaviour), we will need an expensive
+ algorithm to locate a partial symtab or symtab via an address.
+ To avoid this penalty for normal object files, we use this flag,
+ whose setting is determined upon symbol table read in. */
+
+#define OBJF_REORDERED (2 << 1) /* Functions are reordered */
+
/* The object file that the main symbol table was loaded from (e.g. the
argument to the "symbol-file" or "file" command). */
/* Declarations for functions defined in objfiles.c */
-extern struct objfile *allocate_objfile PARAMS ((bfd *, int));
+extern struct objfile *
+allocate_objfile PARAMS ((bfd *, int));
-int build_objfile_section_table PARAMS ((struct objfile *));
+extern int
+build_objfile_section_table PARAMS ((struct objfile *));
-extern void unlink_objfile PARAMS ((struct objfile *));
+extern void
+unlink_objfile PARAMS ((struct objfile *));
-extern void free_objfile PARAMS ((struct objfile *));
+extern void
+free_objfile PARAMS ((struct objfile *));
extern void
free_all_objfiles PARAMS ((void));
(obj) != NULL? ((nxt)=(obj)->next,1) :0; \
(obj) = (nxt))
-
/* Traverse all symtabs in one objfile. */
#define ALL_OBJFILE_SYMTABS(objfile, s) \
#define ALL_OBJFILE_MSYMBOLS(objfile, m) \
for ((m) = (objfile) -> msymbols; SYMBOL_NAME(m) != NULL; (m)++)
-
/* Traverse all symtabs in all objfiles. */
#define ALL_SYMTABS(objfile, s) \