Commit | Line | Data |
---|---|---|
c906108c | 1 | /* Definitions for symbol file management in GDB. |
af5f3db6 AC |
2 | |
3 | Copyright 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, | |
4 | 2001, 2002 Free Software Foundation, Inc. | |
c906108c | 5 | |
c5aa993b | 6 | This file is part of GDB. |
c906108c | 7 | |
c5aa993b JM |
8 | This program is free software; you can redistribute it and/or modify |
9 | it under the terms of the GNU General Public License as published by | |
10 | the Free Software Foundation; either version 2 of the License, or | |
11 | (at your option) any later version. | |
c906108c | 12 | |
c5aa993b JM |
13 | This program is distributed in the hope that it will be useful, |
14 | but WITHOUT ANY WARRANTY; without even the implied warranty of | |
15 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the | |
16 | GNU General Public License for more details. | |
c906108c | 17 | |
c5aa993b JM |
18 | You should have received a copy of the GNU General Public License |
19 | along with this program; if not, write to the Free Software | |
20 | Foundation, Inc., 59 Temple Place - Suite 330, | |
21 | Boston, MA 02111-1307, USA. */ | |
c906108c SS |
22 | |
23 | #if !defined (OBJFILES_H) | |
24 | #define OBJFILES_H | |
25 | ||
af5f3db6 | 26 | struct bcache; |
08c0b5bc | 27 | |
c906108c SS |
28 | /* This structure maintains information on a per-objfile basis about the |
29 | "entry point" of the objfile, and the scope within which the entry point | |
30 | exists. It is possible that gdb will see more than one objfile that is | |
31 | executable, each with its own entry point. | |
32 | ||
33 | For example, for dynamically linked executables in SVR4, the dynamic linker | |
34 | code is contained within the shared C library, which is actually executable | |
35 | and is run by the kernel first when an exec is done of a user executable | |
36 | that is dynamically linked. The dynamic linker within the shared C library | |
37 | then maps in the various program segments in the user executable and jumps | |
38 | to the user executable's recorded entry point, as if the call had been made | |
39 | directly by the kernel. | |
40 | ||
41 | The traditional gdb method of using this info is to use the recorded entry | |
42 | point to set the variables entry_file_lowpc and entry_file_highpc from | |
43 | the debugging information, where these values are the starting address | |
44 | (inclusive) and ending address (exclusive) of the instruction space in the | |
45 | executable which correspond to the "startup file", I.E. crt0.o in most | |
46 | cases. This file is assumed to be a startup file and frames with pc's | |
47 | inside it are treated as nonexistent. Setting these variables is necessary | |
48 | so that backtraces do not fly off the bottom of the stack. | |
49 | ||
50 | Gdb also supports an alternate method to avoid running off the bottom | |
51 | of the stack. | |
52 | ||
53 | There are two frames that are "special", the frame for the function | |
54 | containing the process entry point, since it has no predecessor frame, | |
55 | and the frame for the function containing the user code entry point | |
56 | (the main() function), since all the predecessor frames are for the | |
57 | process startup code. Since we have no guarantee that the linked | |
58 | in startup modules have any debugging information that gdb can use, | |
59 | we need to avoid following frame pointers back into frames that might | |
60 | have been built in the startup code, as we might get hopelessly | |
61 | confused. However, we almost always have debugging information | |
62 | available for main(). | |
63 | ||
64 | These variables are used to save the range of PC values which are valid | |
65 | within the main() function and within the function containing the process | |
66 | entry point. If we always consider the frame for main() as the outermost | |
67 | frame when debugging user code, and the frame for the process entry | |
68 | point function as the outermost frame when debugging startup code, then | |
69 | all we have to do is have FRAME_CHAIN_VALID return false whenever a | |
70 | frame's current PC is within the range specified by these variables. | |
71 | In essence, we set "ceilings" in the frame chain beyond which we will | |
72 | not proceed when following the frame chain back up the stack. | |
73 | ||
74 | A nice side effect is that we can still debug startup code without | |
75 | running off the end of the frame chain, assuming that we have usable | |
76 | debugging information in the startup modules, and if we choose to not | |
77 | use the block at main, or can't find it for some reason, everything | |
78 | still works as before. And if we have no startup code debugging | |
79 | information but we do have usable information for main(), backtraces | |
80 | from user code don't go wandering off into the startup code. | |
81 | ||
82 | To use this method, define your FRAME_CHAIN_VALID macro like: | |
83 | ||
c5aa993b JM |
84 | #define FRAME_CHAIN_VALID(chain, thisframe) \ |
85 | (chain != 0 \ | |
86 | && !(inside_main_func ((thisframe)->pc)) \ | |
87 | && !(inside_entry_func ((thisframe)->pc))) | |
c906108c SS |
88 | |
89 | and add initializations of the four scope controlling variables inside | |
90 | the object file / debugging information processing modules. */ | |
91 | ||
92 | struct entry_info | |
c5aa993b | 93 | { |
c906108c | 94 | |
c5aa993b JM |
95 | /* The value we should use for this objects entry point. |
96 | The illegal/unknown value needs to be something other than 0, ~0 | |
97 | for instance, which is much less likely than 0. */ | |
c906108c | 98 | |
c5aa993b | 99 | CORE_ADDR entry_point; |
c906108c | 100 | |
c5aa993b | 101 | #define INVALID_ENTRY_POINT (~0) /* ~0 will not be in any file, we hope. */ |
c906108c | 102 | |
c5aa993b JM |
103 | /* Start (inclusive) and end (exclusive) of function containing the |
104 | entry point. */ | |
c906108c | 105 | |
c5aa993b JM |
106 | CORE_ADDR entry_func_lowpc; |
107 | CORE_ADDR entry_func_highpc; | |
c906108c | 108 | |
c5aa993b JM |
109 | /* Start (inclusive) and end (exclusive) of object file containing the |
110 | entry point. */ | |
c906108c | 111 | |
c5aa993b JM |
112 | CORE_ADDR entry_file_lowpc; |
113 | CORE_ADDR entry_file_highpc; | |
114 | ||
115 | /* Start (inclusive) and end (exclusive) of the user code main() function. */ | |
116 | ||
117 | CORE_ADDR main_func_lowpc; | |
118 | CORE_ADDR main_func_highpc; | |
c906108c SS |
119 | |
120 | /* Use these values when any of the above ranges is invalid. */ | |
121 | ||
122 | /* We use these values because it guarantees that there is no number that is | |
123 | both >= LOWPC && < HIGHPC. It is also highly unlikely that 3 is a valid | |
124 | module or function start address (as opposed to 0). */ | |
125 | ||
126 | #define INVALID_ENTRY_LOWPC (3) | |
127 | #define INVALID_ENTRY_HIGHPC (1) | |
128 | ||
c5aa993b | 129 | }; |
c906108c SS |
130 | |
131 | /* Sections in an objfile. | |
132 | ||
133 | It is strange that we have both this notion of "sections" | |
134 | and the one used by section_offsets. Section as used | |
135 | here, (currently at least) means a BFD section, and the sections | |
136 | are set up from the BFD sections in allocate_objfile. | |
137 | ||
138 | The sections in section_offsets have their meaning determined by | |
139 | the symbol format, and they are set up by the sym_offsets function | |
140 | for that symbol file format. | |
141 | ||
142 | I'm not sure this could or should be changed, however. */ | |
143 | ||
c5aa993b JM |
144 | struct obj_section |
145 | { | |
146 | CORE_ADDR addr; /* lowest address in section */ | |
147 | CORE_ADDR endaddr; /* 1+highest address in section */ | |
c906108c | 148 | |
c5aa993b JM |
149 | /* This field is being used for nefarious purposes by syms_from_objfile. |
150 | It is said to be redundant with section_offsets; it's not really being | |
151 | used that way, however, it's some sort of hack I don't understand | |
152 | and am not going to try to eliminate (yet, anyway). FIXME. | |
c906108c | 153 | |
c5aa993b JM |
154 | It was documented as "offset between (end)addr and actual memory |
155 | addresses", but that's not true; addr & endaddr are actual memory | |
156 | addresses. */ | |
157 | CORE_ADDR offset; | |
c906108c | 158 | |
c5aa993b | 159 | sec_ptr the_bfd_section; /* BFD section pointer */ |
c906108c | 160 | |
c5aa993b JM |
161 | /* Objfile this section is part of. */ |
162 | struct objfile *objfile; | |
c906108c | 163 | |
c5aa993b JM |
164 | /* True if this "overlay section" is mapped into an "overlay region". */ |
165 | int ovly_mapped; | |
166 | }; | |
c906108c SS |
167 | |
168 | /* An import entry contains information about a symbol that | |
169 | is used in this objfile but not defined in it, and so needs | |
170 | to be imported from some other objfile */ | |
c5aa993b JM |
171 | /* Currently we just store the name; no attributes. 1997-08-05 */ |
172 | typedef char *ImportEntry; | |
c906108c SS |
173 | |
174 | ||
175 | /* An export entry contains information about a symbol that | |
176 | is defined in this objfile and available for use in other | |
c5aa993b JM |
177 | objfiles */ |
178 | typedef struct | |
179 | { | |
180 | char *name; /* name of exported symbol */ | |
181 | int address; /* offset subject to relocation */ | |
182 | /* Currently no other attributes 1997-08-05 */ | |
183 | } | |
184 | ExportEntry; | |
c906108c SS |
185 | |
186 | ||
c906108c SS |
187 | /* The "objstats" structure provides a place for gdb to record some |
188 | interesting information about its internal state at runtime, on a | |
189 | per objfile basis, such as information about the number of symbols | |
190 | read, size of string table (if any), etc. */ | |
191 | ||
c5aa993b JM |
192 | struct objstats |
193 | { | |
194 | int n_minsyms; /* Number of minimal symbols read */ | |
195 | int n_psyms; /* Number of partial symbols read */ | |
196 | int n_syms; /* Number of full symbols read */ | |
197 | int n_stabs; /* Number of ".stabs" read (if applicable) */ | |
198 | int n_types; /* Number of types */ | |
199 | int sz_strtab; /* Size of stringtable, (if applicable) */ | |
200 | }; | |
c906108c SS |
201 | |
202 | #define OBJSTAT(objfile, expr) (objfile -> stats.expr) | |
203 | #define OBJSTATS struct objstats stats | |
a14ed312 KB |
204 | extern void print_objfile_statistics (void); |
205 | extern void print_symbol_bcache_statistics (void); | |
c906108c | 206 | |
9227b5eb | 207 | /* Number of entries in the minimal symbol hash table. */ |
375f3d86 | 208 | #define MINIMAL_SYMBOL_HASH_SIZE 2039 |
9227b5eb | 209 | |
c906108c SS |
210 | /* Master structure for keeping track of each file from which |
211 | gdb reads symbols. There are several ways these get allocated: 1. | |
212 | The main symbol file, symfile_objfile, set by the symbol-file command, | |
213 | 2. Additional symbol files added by the add-symbol-file command, | |
214 | 3. Shared library objfiles, added by ADD_SOLIB, 4. symbol files | |
215 | for modules that were loaded when GDB attached to a remote system | |
216 | (see remote-vx.c). */ | |
217 | ||
218 | struct objfile | |
c5aa993b | 219 | { |
c906108c | 220 | |
c5aa993b JM |
221 | /* All struct objfile's are chained together by their next pointers. |
222 | The global variable "object_files" points to the first link in this | |
223 | chain. | |
c906108c | 224 | |
c5aa993b JM |
225 | FIXME: There is a problem here if the objfile is reusable, and if |
226 | multiple users are to be supported. The problem is that the objfile | |
227 | list is linked through a member of the objfile struct itself, which | |
228 | is only valid for one gdb process. The list implementation needs to | |
229 | be changed to something like: | |
c906108c | 230 | |
c5aa993b | 231 | struct list {struct list *next; struct objfile *objfile}; |
c906108c | 232 | |
c5aa993b JM |
233 | where the list structure is completely maintained separately within |
234 | each gdb process. */ | |
c906108c | 235 | |
c5aa993b | 236 | struct objfile *next; |
c906108c | 237 | |
c5aa993b | 238 | /* The object file's name. Malloc'd; free it if you free this struct. */ |
c906108c | 239 | |
c5aa993b | 240 | char *name; |
c906108c | 241 | |
c5aa993b | 242 | /* Some flag bits for this objfile. */ |
c906108c | 243 | |
c5aa993b | 244 | unsigned short flags; |
c906108c | 245 | |
c5aa993b JM |
246 | /* Each objfile points to a linked list of symtabs derived from this file, |
247 | one symtab structure for each compilation unit (source file). Each link | |
248 | in the symtab list contains a backpointer to this objfile. */ | |
c906108c | 249 | |
c5aa993b | 250 | struct symtab *symtabs; |
c906108c | 251 | |
c5aa993b JM |
252 | /* Each objfile points to a linked list of partial symtabs derived from |
253 | this file, one partial symtab structure for each compilation unit | |
254 | (source file). */ | |
c906108c | 255 | |
c5aa993b | 256 | struct partial_symtab *psymtabs; |
c906108c | 257 | |
c5aa993b | 258 | /* List of freed partial symtabs, available for re-use */ |
c906108c | 259 | |
c5aa993b | 260 | struct partial_symtab *free_psymtabs; |
c906108c | 261 | |
c5aa993b JM |
262 | /* The object file's BFD. Can be null if the objfile contains only |
263 | minimal symbols, e.g. the run time common symbols for SunOS4. */ | |
c906108c | 264 | |
c5aa993b | 265 | bfd *obfd; |
c906108c | 266 | |
c5aa993b JM |
267 | /* The modification timestamp of the object file, as of the last time |
268 | we read its symbols. */ | |
c906108c | 269 | |
c5aa993b | 270 | long mtime; |
c906108c | 271 | |
c5aa993b JM |
272 | /* Obstacks to hold objects that should be freed when we load a new symbol |
273 | table from this object file. */ | |
c906108c | 274 | |
c5aa993b JM |
275 | struct obstack psymbol_obstack; /* Partial symbols */ |
276 | struct obstack symbol_obstack; /* Full symbols */ | |
277 | struct obstack type_obstack; /* Types */ | |
c906108c | 278 | |
c5aa993b JM |
279 | /* A byte cache where we can stash arbitrary "chunks" of bytes that |
280 | will not change. */ | |
c906108c | 281 | |
af5f3db6 AC |
282 | struct bcache *psymbol_cache; /* Byte cache for partial syms */ |
283 | struct bcache *macro_cache; /* Byte cache for macros */ | |
c906108c | 284 | |
c5aa993b JM |
285 | /* Vectors of all partial symbols read in from file. The actual data |
286 | is stored in the psymbol_obstack. */ | |
c906108c | 287 | |
c5aa993b JM |
288 | struct psymbol_allocation_list global_psymbols; |
289 | struct psymbol_allocation_list static_psymbols; | |
c906108c | 290 | |
c5aa993b JM |
291 | /* Each file contains a pointer to an array of minimal symbols for all |
292 | global symbols that are defined within the file. The array is terminated | |
293 | by a "null symbol", one that has a NULL pointer for the name and a zero | |
294 | value for the address. This makes it easy to walk through the array | |
295 | when passed a pointer to somewhere in the middle of it. There is also | |
296 | a count of the number of symbols, which does not include the terminating | |
297 | null symbol. The array itself, as well as all the data that it points | |
298 | to, should be allocated on the symbol_obstack for this file. */ | |
c906108c | 299 | |
c5aa993b JM |
300 | struct minimal_symbol *msymbols; |
301 | int minimal_symbol_count; | |
c906108c | 302 | |
9227b5eb JB |
303 | /* This is a hash table used to index the minimal symbols by name. */ |
304 | ||
305 | struct minimal_symbol *msymbol_hash[MINIMAL_SYMBOL_HASH_SIZE]; | |
306 | ||
307 | /* This hash table is used to index the minimal symbols by their | |
308 | demangled names. */ | |
309 | ||
310 | struct minimal_symbol *msymbol_demangled_hash[MINIMAL_SYMBOL_HASH_SIZE]; | |
311 | ||
c5aa993b JM |
312 | /* For object file formats which don't specify fundamental types, gdb |
313 | can create such types. For now, it maintains a vector of pointers | |
314 | to these internally created fundamental types on a per objfile basis, | |
315 | however it really should ultimately keep them on a per-compilation-unit | |
316 | basis, to account for linkage-units that consist of a number of | |
317 | compilation units that may have different fundamental types, such as | |
318 | linking C modules with ADA modules, or linking C modules that are | |
319 | compiled with 32-bit ints with C modules that are compiled with 64-bit | |
320 | ints (not inherently evil with a smarter linker). */ | |
c906108c | 321 | |
c5aa993b | 322 | struct type **fundamental_types; |
c906108c | 323 | |
c5aa993b JM |
324 | /* The mmalloc() malloc-descriptor for this objfile if we are using |
325 | the memory mapped malloc() package to manage storage for this objfile's | |
326 | data. NULL if we are not. */ | |
c906108c | 327 | |
c5aa993b | 328 | PTR md; |
c906108c | 329 | |
c5aa993b JM |
330 | /* The file descriptor that was used to obtain the mmalloc descriptor |
331 | for this objfile. If we call mmalloc_detach with the malloc descriptor | |
332 | we should then close this file descriptor. */ | |
c906108c | 333 | |
c5aa993b | 334 | int mmfd; |
c906108c | 335 | |
c5aa993b JM |
336 | /* Structure which keeps track of functions that manipulate objfile's |
337 | of the same type as this objfile. I.E. the function to read partial | |
338 | symbols for example. Note that this structure is in statically | |
339 | allocated memory, and is shared by all objfiles that use the | |
340 | object module reader of this type. */ | |
c906108c | 341 | |
c5aa993b | 342 | struct sym_fns *sf; |
c906108c | 343 | |
c5aa993b JM |
344 | /* The per-objfile information about the entry point, the scope (file/func) |
345 | containing the entry point, and the scope of the user's main() func. */ | |
c906108c | 346 | |
c5aa993b | 347 | struct entry_info ei; |
c906108c | 348 | |
c5aa993b JM |
349 | /* Information about stabs. Will be filled in with a dbx_symfile_info |
350 | struct by those readers that need it. */ | |
c906108c | 351 | |
c5aa993b | 352 | struct dbx_symfile_info *sym_stab_info; |
c906108c | 353 | |
c5aa993b JM |
354 | /* Hook for information for use by the symbol reader (currently used |
355 | for information shared by sym_init and sym_read). It is | |
356 | typically a pointer to malloc'd memory. The symbol reader's finish | |
357 | function is responsible for freeing the memory thusly allocated. */ | |
c906108c | 358 | |
c5aa993b | 359 | PTR sym_private; |
c906108c | 360 | |
c5aa993b JM |
361 | /* Hook for target-architecture-specific information. This must |
362 | point to memory allocated on one of the obstacks in this objfile, | |
363 | so that it gets freed automatically when reading a new object | |
364 | file. */ | |
c906108c | 365 | |
c5f10366 | 366 | void *obj_private; |
c906108c | 367 | |
c5aa993b JM |
368 | /* Set of relocation offsets to apply to each section. |
369 | Currently on the psymbol_obstack (which makes no sense, but I'm | |
370 | not sure it's harming anything). | |
c906108c | 371 | |
c5aa993b JM |
372 | These offsets indicate that all symbols (including partial and |
373 | minimal symbols) which have been read have been relocated by this | |
374 | much. Symbols which are yet to be read need to be relocated by | |
375 | it. */ | |
c906108c | 376 | |
c5aa993b JM |
377 | struct section_offsets *section_offsets; |
378 | int num_sections; | |
c906108c | 379 | |
b8fbeb18 EZ |
380 | /* Indexes in the section_offsets array. These are initialized by the |
381 | *_symfile_offsets() family of functions (som_symfile_offsets, | |
382 | xcoff_symfile_offsets, default_symfile_offsets). In theory they | |
383 | should correspond to the section indexes used by bfd for the | |
384 | current objfile. The exception to this for the time being is the | |
385 | SOM version. */ | |
386 | ||
387 | int sect_index_text; | |
388 | int sect_index_data; | |
389 | int sect_index_bss; | |
390 | int sect_index_rodata; | |
391 | ||
96baa820 | 392 | /* These pointers are used to locate the section table, which |
5c44784c | 393 | among other things, is used to map pc addresses into sections. |
96baa820 JM |
394 | SECTIONS points to the first entry in the table, and |
395 | SECTIONS_END points to the first location past the last entry | |
396 | in the table. Currently the table is stored on the | |
397 | psymbol_obstack (which makes no sense, but I'm not sure it's | |
398 | harming anything). */ | |
c906108c | 399 | |
c5aa993b JM |
400 | struct obj_section |
401 | *sections, *sections_end; | |
c906108c | 402 | |
c5aa993b JM |
403 | /* two auxiliary fields, used to hold the fp of separate symbol files */ |
404 | FILE *auxf1, *auxf2; | |
c906108c | 405 | |
c5aa993b JM |
406 | /* Imported symbols */ |
407 | ImportEntry *import_list; | |
408 | int import_list_size; | |
c906108c | 409 | |
c5aa993b JM |
410 | /* Exported symbols */ |
411 | ExportEntry *export_list; | |
412 | int export_list_size; | |
c906108c | 413 | |
c5aa993b JM |
414 | /* Place to stash various statistics about this objfile */ |
415 | OBJSTATS; | |
416 | }; | |
c906108c SS |
417 | |
418 | /* Defines for the objfile flag word. */ | |
419 | ||
420 | /* Gdb can arrange to allocate storage for all objects related to a | |
421 | particular objfile in a designated section of its address space, | |
422 | managed at a low level by mmap() and using a special version of | |
423 | malloc that handles malloc/free/realloc on top of the mmap() interface. | |
424 | This allows the "internal gdb state" for a particular objfile to be | |
425 | dumped to a gdb state file and subsequently reloaded at a later time. */ | |
426 | ||
427 | #define OBJF_MAPPED (1 << 0) /* Objfile data is mmap'd */ | |
428 | ||
429 | /* When using mapped/remapped predigested gdb symbol information, we need | |
430 | a flag that indicates that we have previously done an initial symbol | |
431 | table read from this particular objfile. We can't just look for the | |
432 | absence of any of the three symbol tables (msymbols, psymtab, symtab) | |
433 | because if the file has no symbols for example, none of these will | |
434 | exist. */ | |
435 | ||
436 | #define OBJF_SYMS (1 << 1) /* Have tried to read symbols */ | |
437 | ||
438 | /* When an object file has its functions reordered (currently Irix-5.2 | |
439 | shared libraries exhibit this behaviour), we will need an expensive | |
440 | algorithm to locate a partial symtab or symtab via an address. | |
441 | To avoid this penalty for normal object files, we use this flag, | |
442 | whose setting is determined upon symbol table read in. */ | |
443 | ||
444 | #define OBJF_REORDERED (1 << 2) /* Functions are reordered */ | |
c5aa993b | 445 | |
2df3850c JM |
446 | /* Distinguish between an objfile for a shared library and a "vanilla" |
447 | objfile. (If not set, the objfile may still actually be a solib. | |
448 | This can happen if the user created the objfile by using the | |
449 | add-symbol-file command. GDB doesn't in that situation actually | |
450 | check whether the file is a solib. Rather, the target's | |
451 | implementation of the solib interface is responsible for setting | |
452 | this flag when noticing solibs used by an inferior.) */ | |
c906108c | 453 | |
c5aa993b | 454 | #define OBJF_SHARED (1 << 3) /* From a shared library */ |
c906108c | 455 | |
2acceee2 JM |
456 | /* User requested that this objfile be read in it's entirety. */ |
457 | ||
458 | #define OBJF_READNOW (1 << 4) /* Immediate full read */ | |
459 | ||
2df3850c JM |
460 | /* This objfile was created because the user explicitly caused it |
461 | (e.g., used the add-symbol-file command). This bit offers a way | |
462 | for run_command to remove old objfile entries which are no longer | |
463 | valid (i.e., are associated with an old inferior), but to preserve | |
464 | ones that the user explicitly loaded via the add-symbol-file | |
465 | command. */ | |
466 | ||
467 | #define OBJF_USERLOADED (1 << 5) /* User loaded */ | |
468 | ||
c906108c SS |
469 | /* The object file that the main symbol table was loaded from (e.g. the |
470 | argument to the "symbol-file" or "file" command). */ | |
471 | ||
472 | extern struct objfile *symfile_objfile; | |
473 | ||
474 | /* The object file that contains the runtime common minimal symbols | |
475 | for SunOS4. Note that this objfile has no associated BFD. */ | |
476 | ||
477 | extern struct objfile *rt_common_objfile; | |
478 | ||
479 | /* When we need to allocate a new type, we need to know which type_obstack | |
480 | to allocate the type on, since there is one for each objfile. The places | |
481 | where types are allocated are deeply buried in function call hierarchies | |
482 | which know nothing about objfiles, so rather than trying to pass a | |
483 | particular objfile down to them, we just do an end run around them and | |
484 | set current_objfile to be whatever objfile we expect to be using at the | |
485 | time types are being allocated. For instance, when we start reading | |
486 | symbols for a particular objfile, we set current_objfile to point to that | |
487 | objfile, and when we are done, we set it back to NULL, to ensure that we | |
488 | never put a type someplace other than where we are expecting to put it. | |
489 | FIXME: Maybe we should review the entire type handling system and | |
490 | see if there is a better way to avoid this problem. */ | |
491 | ||
492 | extern struct objfile *current_objfile; | |
493 | ||
494 | /* All known objfiles are kept in a linked list. This points to the | |
495 | root of this list. */ | |
496 | ||
497 | extern struct objfile *object_files; | |
498 | ||
499 | /* Declarations for functions defined in objfiles.c */ | |
500 | ||
a14ed312 | 501 | extern struct objfile *allocate_objfile (bfd *, int); |
c906108c | 502 | |
a14ed312 | 503 | extern int build_objfile_section_table (struct objfile *); |
c906108c | 504 | |
a14ed312 | 505 | extern void objfile_to_front (struct objfile *); |
c906108c | 506 | |
a14ed312 | 507 | extern void unlink_objfile (struct objfile *); |
c906108c | 508 | |
a14ed312 | 509 | extern void free_objfile (struct objfile *); |
c906108c | 510 | |
74b7792f AC |
511 | extern struct cleanup *make_cleanup_free_objfile (struct objfile *); |
512 | ||
a14ed312 | 513 | extern void free_all_objfiles (void); |
c906108c | 514 | |
a14ed312 | 515 | extern void objfile_relocate (struct objfile *, struct section_offsets *); |
c906108c | 516 | |
a14ed312 | 517 | extern int have_partial_symbols (void); |
c906108c | 518 | |
a14ed312 | 519 | extern int have_full_symbols (void); |
c906108c SS |
520 | |
521 | /* This operation deletes all objfile entries that represent solibs that | |
522 | weren't explicitly loaded by the user, via e.g., the add-symbol-file | |
523 | command. | |
c5aa993b | 524 | */ |
a14ed312 | 525 | extern void objfile_purge_solibs (void); |
c906108c SS |
526 | |
527 | /* Functions for dealing with the minimal symbol table, really a misc | |
528 | address<->symbol mapping for things we don't have debug symbols for. */ | |
529 | ||
a14ed312 | 530 | extern int have_minimal_symbols (void); |
c906108c | 531 | |
a14ed312 | 532 | extern struct obj_section *find_pc_section (CORE_ADDR pc); |
c906108c | 533 | |
a14ed312 KB |
534 | extern struct obj_section *find_pc_sect_section (CORE_ADDR pc, |
535 | asection * section); | |
c906108c | 536 | |
a14ed312 | 537 | extern int in_plt_section (CORE_ADDR, char *); |
c906108c | 538 | |
a14ed312 | 539 | extern int is_in_import_list (char *, struct objfile *); |
7be570e7 | 540 | |
c906108c SS |
541 | /* Traverse all object files. ALL_OBJFILES_SAFE works even if you delete |
542 | the objfile during the traversal. */ | |
543 | ||
544 | #define ALL_OBJFILES(obj) \ | |
545 | for ((obj) = object_files; (obj) != NULL; (obj) = (obj)->next) | |
546 | ||
547 | #define ALL_OBJFILES_SAFE(obj,nxt) \ | |
548 | for ((obj) = object_files; \ | |
549 | (obj) != NULL? ((nxt)=(obj)->next,1) :0; \ | |
550 | (obj) = (nxt)) | |
551 | ||
552 | /* Traverse all symtabs in one objfile. */ | |
553 | ||
554 | #define ALL_OBJFILE_SYMTABS(objfile, s) \ | |
555 | for ((s) = (objfile) -> symtabs; (s) != NULL; (s) = (s) -> next) | |
556 | ||
557 | /* Traverse all psymtabs in one objfile. */ | |
558 | ||
559 | #define ALL_OBJFILE_PSYMTABS(objfile, p) \ | |
560 | for ((p) = (objfile) -> psymtabs; (p) != NULL; (p) = (p) -> next) | |
561 | ||
562 | /* Traverse all minimal symbols in one objfile. */ | |
563 | ||
564 | #define ALL_OBJFILE_MSYMBOLS(objfile, m) \ | |
565 | for ((m) = (objfile) -> msymbols; SYMBOL_NAME(m) != NULL; (m)++) | |
566 | ||
567 | /* Traverse all symtabs in all objfiles. */ | |
568 | ||
569 | #define ALL_SYMTABS(objfile, s) \ | |
570 | ALL_OBJFILES (objfile) \ | |
571 | ALL_OBJFILE_SYMTABS (objfile, s) | |
572 | ||
573 | /* Traverse all psymtabs in all objfiles. */ | |
574 | ||
575 | #define ALL_PSYMTABS(objfile, p) \ | |
576 | ALL_OBJFILES (objfile) \ | |
577 | ALL_OBJFILE_PSYMTABS (objfile, p) | |
578 | ||
579 | /* Traverse all minimal symbols in all objfiles. */ | |
580 | ||
581 | #define ALL_MSYMBOLS(objfile, m) \ | |
582 | ALL_OBJFILES (objfile) \ | |
583 | if ((objfile)->msymbols) \ | |
584 | ALL_OBJFILE_MSYMBOLS (objfile, m) | |
585 | ||
586 | #define ALL_OBJFILE_OSECTIONS(objfile, osect) \ | |
587 | for (osect = objfile->sections; osect < objfile->sections_end; osect++) | |
588 | ||
589 | #define ALL_OBJSECTIONS(objfile, osect) \ | |
590 | ALL_OBJFILES (objfile) \ | |
591 | ALL_OBJFILE_OSECTIONS (objfile, osect) | |
592 | ||
b8fbeb18 | 593 | #define SECT_OFF_DATA(objfile) \ |
8e65ff28 AC |
594 | ((objfile->sect_index_data == -1) \ |
595 | ? (internal_error (__FILE__, __LINE__, "sect_index_data not initialized"), -1) \ | |
596 | : objfile->sect_index_data) | |
b8fbeb18 EZ |
597 | |
598 | #define SECT_OFF_RODATA(objfile) \ | |
8e65ff28 AC |
599 | ((objfile->sect_index_rodata == -1) \ |
600 | ? (internal_error (__FILE__, __LINE__, "sect_index_rodata not initialized"), -1) \ | |
601 | : objfile->sect_index_rodata) | |
b8fbeb18 EZ |
602 | |
603 | #define SECT_OFF_TEXT(objfile) \ | |
8e65ff28 AC |
604 | ((objfile->sect_index_text == -1) \ |
605 | ? (internal_error (__FILE__, __LINE__, "sect_index_text not initialized"), -1) \ | |
606 | : objfile->sect_index_text) | |
b8fbeb18 | 607 | |
a4c8257b EZ |
608 | /* Sometimes the .bss section is missing from the objfile, so we don't |
609 | want to die here. Let the users of SECT_OFF_BSS deal with an | |
610 | uninitialized section index. */ | |
611 | #define SECT_OFF_BSS(objfile) (objfile)->sect_index_bss | |
b8fbeb18 | 612 | |
c5aa993b | 613 | #endif /* !defined (OBJFILES_H) */ |