/* Definitions for symbol file management in GDB.
- Copyright (C) 1992 Free Software Foundation, Inc.
+ Copyright (C) 1992, 1993, 1994, 1995 Free Software Foundation, Inc.
This file is part of GDB.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
-Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. */
+Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */
#if !defined (OBJFILES_H)
#define OBJFILES_H
/* 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 partial_symtab *free_psymtabs;
- /* The object file's BFD. Can be null, in which case bfd_open (name) and
- put the result here. */
+ /* The object file's BFD. Can be null if the objfile contains only
+ minimal symbols, e.g. the run time common symbols for SunOS4. */
bfd *obfd;
by a "null symbol", one that has a NULL pointer for the name and a zero
value for the address. This makes it easy to walk through the array
when passed a pointer to somewhere in the middle of it. There is also
- a count of the number of symbols, which does include the terminating
+ a count of the number of symbols, which does not include the terminating
null symbol. The array itself, as well as all the data that it points
to, should be allocated on the symbol_obstack for this file. */
/* 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). */
extern struct objfile *symfile_objfile;
+/* The object file that contains the runtime common minimal symbols
+ for SunOS4. Note that this objfile has no associated BFD. */
+
+extern struct objfile *rt_common_objfile;
+
/* When we need to allocate a new type, we need to know which type_obstack
to allocate the type on, since there is one for each objfile. The places
where types are allocated are deeply buried in function call hierarchies
/* 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 objfile_to_front PARAMS ((struct objfile *));
-extern void free_objfile PARAMS ((struct objfile *));
+extern void
+unlink_objfile PARAMS ((struct objfile *));
extern void
-free_all_objfiles PARAMS ((void));
+free_objfile PARAMS ((struct objfile *));
-extern struct objfile * find_pc_objfile PARAMS ((CORE_ADDR));
+extern void
+free_all_objfiles PARAMS ((void));
extern void
objfile_relocate PARAMS ((struct objfile *, struct section_offsets *));
(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) \