Commit | Line | Data |
---|---|---|
e505224d PB |
1 | \input texinfo |
2 | @setfilename stabs.info | |
3 | ||
6fe91f2c | 4 | @c @finalout |
a9ded3ac | 5 | |
e505224d PB |
6 | @ifinfo |
7 | @format | |
8 | START-INFO-DIR-ENTRY | |
8a6d5d4f | 9 | * Stabs:: The "stabs" debugging information format. |
e505224d PB |
10 | END-INFO-DIR-ENTRY |
11 | @end format | |
12 | @end ifinfo | |
13 | ||
14 | @ifinfo | |
8c59ee11 | 15 | This document describes the stabs debugging symbol tables. |
e505224d | 16 | |
6fe91f2c | 17 | Copyright 1992, 1993 Free Software Foundation, Inc. |
ee5e0932 JK |
18 | Contributed by Cygnus Support. Written by Julia Menapace, Jim Kingdon, |
19 | and David MacKenzie. | |
e505224d PB |
20 | |
21 | Permission is granted to make and distribute verbatim copies of | |
22 | this manual provided the copyright notice and this permission notice | |
23 | are preserved on all copies. | |
24 | ||
25 | @ignore | |
26 | Permission is granted to process this file through Tex and print the | |
27 | results, provided the printed document carries copying permission | |
28 | notice identical to this one except for the removal of this paragraph | |
29 | (this paragraph not being relevant to the printed manual). | |
30 | ||
31 | @end ignore | |
32 | Permission is granted to copy or distribute modified versions of this | |
33 | manual under the terms of the GPL (for which purpose this text may be | |
34 | regarded as a program in the language TeX). | |
35 | @end ifinfo | |
36 | ||
139741da | 37 | @setchapternewpage odd |
e505224d PB |
38 | @settitle STABS |
39 | @titlepage | |
139741da | 40 | @title The ``stabs'' debug format |
f958d5cd | 41 | @author Julia Menapace, Jim Kingdon, David MacKenzie |
e505224d PB |
42 | @author Cygnus Support |
43 | @page | |
44 | @tex | |
45 | \def\$#1${{#1}} % Kluge: collect RCS revision info without $...$ | |
46 | \xdef\manvers{\$Revision$} % For use in headers, footers too | |
47 | {\parskip=0pt | |
48 | \hfill Cygnus Support\par | |
49 | \hfill \manvers\par | |
50 | \hfill \TeX{}info \texinfoversion\par | |
51 | } | |
52 | @end tex | |
53 | ||
54 | @vskip 0pt plus 1filll | |
6fe91f2c | 55 | Copyright @copyright{} 1992, 1993 Free Software Foundation, Inc. |
899bafeb | 56 | Contributed by Cygnus Support. |
e505224d PB |
57 | |
58 | Permission is granted to make and distribute verbatim copies of | |
59 | this manual provided the copyright notice and this permission notice | |
60 | are preserved on all copies. | |
61 | ||
62 | @end titlepage | |
63 | ||
899bafeb RP |
64 | @ifinfo |
65 | @node Top | |
66 | @top The "stabs" representation of debugging information | |
e505224d | 67 | |
6ae55c65 | 68 | This document describes the stabs debugging format. |
e505224d PB |
69 | |
70 | @menu | |
8eb5e289 | 71 | * Overview:: Overview of stabs |
bf9d2537 | 72 | * Program Structure:: Encoding of the structure of the program |
6897f9ec | 73 | * Constants:: Constants |
6fe91f2c | 74 | * Variables:: |
8c59ee11 | 75 | * Types:: Type definitions |
bf9d2537 | 76 | * Symbol Tables:: Symbol information in symbol tables |
8eb5e289 | 77 | * Cplusplus:: Appendixes: |
bf9d2537 DM |
78 | * Stab Types:: Symbol types in a.out files |
79 | * Symbol Descriptors:: Table of symbol descriptors | |
80 | * Type Descriptors:: Table of type descriptors | |
81 | * Expanded Reference:: Reference information by stab type | |
8eb5e289 | 82 | * Questions:: Questions and anomolies |
bf9d2537 | 83 | * XCOFF Differences:: Differences between GNU stabs in a.out |
f958d5cd | 84 | and GNU stabs in XCOFF |
bf9d2537 | 85 | * Sun Differences:: Differences between GNU stabs and Sun |
139741da | 86 | native stabs |
bf9d2537 DM |
87 | * Stabs In ELF:: Stabs in an ELF file. |
88 | * Symbol Types Index:: Index of symbolic stab symbol type names. | |
e505224d | 89 | @end menu |
899bafeb | 90 | @end ifinfo |
e505224d PB |
91 | |
92 | ||
899bafeb | 93 | @node Overview |
bf9d2537 | 94 | @chapter Overview of Stabs |
e505224d | 95 | |
139741da RP |
96 | @dfn{Stabs} refers to a format for information that describes a program |
97 | to a debugger. This format was apparently invented by | |
534694b3 | 98 | Peter Kessler at |
139741da RP |
99 | the University of California at Berkeley, for the @code{pdx} Pascal |
100 | debugger; the format has spread widely since then. | |
101 | ||
8c59ee11 | 102 | This document is one of the few published sources of documentation on |
dd8126d9 | 103 | stabs. It is believed to be comprehensive for stabs used by C. The |
bf9d2537 DM |
104 | lists of symbol descriptors (@pxref{Symbol Descriptors}) and type |
105 | descriptors (@pxref{Type Descriptors}) are believed to be completely | |
dd8126d9 JK |
106 | comprehensive. Stabs for COBOL-specific features and for variant |
107 | records (used by Pascal and Modula-2) are poorly documented here. | |
108 | ||
109 | Other sources of information on stabs are @cite{Dbx and Dbxtool | |
110 | Interfaces}, 2nd edition, by Sun, 1988, and @cite{AIX Version 3.2 Files | |
111 | Reference}, Fourth Edition, September 1992, "dbx Stabstring Grammar" in | |
112 | the a.out section, page 2-31. This document is believed to incorporate | |
b857d956 | 113 | the information from those two sources except where it explicitly directs |
dd8126d9 | 114 | you to them for more information. |
8c59ee11 | 115 | |
e505224d | 116 | @menu |
8eb5e289 | 117 | * Flow:: Overview of debugging information flow |
bf9d2537 DM |
118 | * Stabs Format:: Overview of stab format |
119 | * String Field:: The string field | |
120 | * C Example:: A simple example in C source | |
121 | * Assembly Code:: The simple example at the assembly level | |
e505224d PB |
122 | @end menu |
123 | ||
899bafeb | 124 | @node Flow |
bf9d2537 | 125 | @section Overview of Debugging Information Flow |
e505224d | 126 | |
139741da | 127 | The GNU C compiler compiles C source in a @file{.c} file into assembly |
6fe91f2c DM |
128 | language in a @file{.s} file, which the assembler translates into |
129 | a @file{.o} file, which the linker combines with other @file{.o} files and | |
139741da | 130 | libraries to produce an executable file. |
e505224d | 131 | |
6fe91f2c DM |
132 | With the @samp{-g} option, GCC puts in the @file{.s} file additional |
133 | debugging information, which is slightly transformed by the assembler | |
134 | and linker, and carried through into the final executable. This | |
135 | debugging information describes features of the source file like line | |
136 | numbers, the types and scopes of variables, and function names, | |
137 | parameters, and scopes. | |
e505224d | 138 | |
6fe91f2c DM |
139 | For some object file formats, the debugging information is encapsulated |
140 | in assembler directives known collectively as @dfn{stab} (symbol table) | |
141 | directives, which are interspersed with the generated code. Stabs are | |
f958d5cd DM |
142 | the native format for debugging information in the a.out and XCOFF |
143 | object file formats. The GNU tools can also emit stabs in the COFF and | |
144 | ECOFF object file formats. | |
e505224d | 145 | |
139741da RP |
146 | The assembler adds the information from stabs to the symbol information |
147 | it places by default in the symbol table and the string table of the | |
148 | @file{.o} file it is building. The linker consolidates the @file{.o} | |
149 | files into one executable file, with one symbol table and one string | |
150 | table. Debuggers use the symbol and string tables in the executable as | |
151 | a source of debugging information about the program. | |
e505224d | 152 | |
bf9d2537 DM |
153 | @node Stabs Format |
154 | @section Overview of Stab Format | |
e505224d | 155 | |
6fe91f2c | 156 | There are three overall formats for stab assembler directives, |
139741da | 157 | differentiated by the first word of the stab. The name of the directive |
6fe91f2c DM |
158 | describes which combination of four possible data fields follows. It is |
159 | either @code{.stabs} (string), @code{.stabn} (number), or @code{.stabd} | |
f958d5cd | 160 | (dot). IBM's XCOFF assembler uses @code{.stabx} (and some other |
63cef7d7 JK |
161 | directives such as @code{.file} and @code{.bi}) instead of |
162 | @code{.stabs}, @code{.stabn} or @code{.stabd}. | |
e505224d PB |
163 | |
164 | The overall format of each class of stab is: | |
165 | ||
166 | @example | |
0a95c18c JK |
167 | .stabs "@var{string}",@var{type},@var{other},@var{desc},@var{value} |
168 | .stabn @var{type},@var{other},@var{desc},@var{value} | |
169 | .stabd @var{type},@var{other},@var{desc} | |
6fe91f2c | 170 | .stabx "@var{string}",@var{value},@var{type},@var{sdb-type} |
e505224d PB |
171 | @end example |
172 | ||
63cef7d7 JK |
173 | @c what is the correct term for "current file location"? My AIX |
174 | @c assembler manual calls it "the value of the current location counter". | |
6fe91f2c | 175 | For @code{.stabn} and @code{.stabd}, there is no @var{string} (the |
bf9d2537 | 176 | @code{n_strx} field is zero; see @ref{Symbol Tables}). For |
6fe91f2c DM |
177 | @code{.stabd}, the @var{value} field is implicit and has the value of |
178 | the current file location. For @code{.stabx}, the @var{sdb-type} field | |
0a95c18c JK |
179 | is unused for stabs and can always be set to zero. The @var{other} |
180 | field is almost always unused and can be set to zero. | |
6fe91f2c DM |
181 | |
182 | The number in the @var{type} field gives some basic information about | |
183 | which type of stab this is (or whether it @emph{is} a stab, as opposed | |
184 | to an ordinary symbol). Each valid type number defines a different stab | |
685a5e86 | 185 | type; further, the stab type defines the exact interpretation of, and |
6fe91f2c | 186 | possible values for, any remaining @var{string}, @var{desc}, or |
bf9d2537 | 187 | @var{value} fields present in the stab. @xref{Stab Types}, for a list |
685a5e86 | 188 | in numeric order of the valid @var{type} field values for stab directives. |
6fe91f2c | 189 | |
bf9d2537 | 190 | @node String Field |
0a95c18c | 191 | @section The String Field |
e505224d | 192 | |
0a95c18c JK |
193 | For most stabs the string field holds the meat of the |
194 | debugging information. The flexible nature of this field | |
195 | is what makes stabs extensible. For some stab types the string field | |
139741da RP |
196 | contains only a name. For other stab types the contents can be a great |
197 | deal more complex. | |
e505224d | 198 | |
0a95c18c | 199 | The overall format of the string field for most stab types is: |
e505224d PB |
200 | |
201 | @example | |
46351197 | 202 | "@var{name}:@var{symbol-descriptor} @var{type-information}" |
e505224d PB |
203 | @end example |
204 | ||
397f9dcd JK |
205 | @var{name} is the name of the symbol represented by the stab; it can |
206 | contain a pair of colons (@pxref{Nested Symbols}). @var{name} can be | |
207 | omitted, which means the stab represents an unnamed object. For | |
208 | example, @samp{:t10=*2} defines type 10 as a pointer to type 2, but does | |
209 | not give the type a name. Omitting the @var{name} field is supported by | |
210 | AIX dbx and GDB after about version 4.8, but not other debuggers. GCC | |
211 | sometimes uses a single space as the name instead of omitting the name | |
212 | altogether; apparently that is supported by most debuggers. | |
e505224d | 213 | |
685a5e86 | 214 | The @var{symbol-descriptor} following the @samp{:} is an alphabetic |
139741da | 215 | character that tells more specifically what kind of symbol the stab |
685a5e86 | 216 | represents. If the @var{symbol-descriptor} is omitted, but type |
139741da | 217 | information follows, then the stab represents a local variable. For a |
bf9d2537 | 218 | list of symbol descriptors, see @ref{Symbol Descriptors}. The @samp{c} |
6fe91f2c DM |
219 | symbol descriptor is an exception in that it is not followed by type |
220 | information. @xref{Constants}. | |
e505224d | 221 | |
685a5e86 DM |
222 | @var{type-information} is either a @var{type-number}, or |
223 | @samp{@var{type-number}=}. A @var{type-number} alone is a type | |
139741da | 224 | reference, referring directly to a type that has already been defined. |
e505224d | 225 | |
685a5e86 | 226 | The @samp{@var{type-number}=} form is a type definition, where the |
e7bb76cc JK |
227 | number represents a new type which is about to be defined. The type |
228 | definition may refer to other types by number, and those type numbers | |
b563c370 JK |
229 | may be followed by @samp{=} and nested definitions. Also, the Lucid |
230 | compiler will repeat @samp{@var{type-number}=} more than once if it | |
231 | wants to define several type numbers at once. | |
e505224d PB |
232 | |
233 | In a type definition, if the character that follows the equals sign is | |
685a5e86 | 234 | non-numeric then it is a @var{type-descriptor}, and tells what kind of |
139741da | 235 | type is about to be defined. Any other values following the |
685a5e86 | 236 | @var{type-descriptor} vary, depending on the @var{type-descriptor}. |
bf9d2537 | 237 | @xref{Type Descriptors}, for a list of @var{type-descriptor} values. If |
685a5e86 DM |
238 | a number follows the @samp{=} then the number is a @var{type-reference}. |
239 | For a full description of types, @ref{Types}. | |
139741da | 240 | |
6897f9ec | 241 | There is an AIX extension for type attributes. Following the @samp{=} |
685a5e86 | 242 | are any number of type attributes. Each one starts with @samp{@@} and |
dd8126d9 JK |
243 | ends with @samp{;}. Debuggers, including AIX's dbx and GDB 4.10, skip |
244 | any type attributes they do not recognize. GDB 4.9 and other versions | |
245 | of dbx may not do this. Because of a conflict with C++ | |
8c59ee11 JK |
246 | (@pxref{Cplusplus}), new attributes should not be defined which begin |
247 | with a digit, @samp{(}, or @samp{-}; GDB may be unable to distinguish | |
248 | those from the C++ type descriptor @samp{@@}. The attributes are: | |
6897f9ec JK |
249 | |
250 | @table @code | |
251 | @item a@var{boundary} | |
8c59ee11 | 252 | @var{boundary} is an integer specifying the alignment. I assume it |
6897f9ec JK |
253 | applies to all variables of this type. |
254 | ||
6897f9ec JK |
255 | @item p@var{integer} |
256 | Pointer class (for checking). Not sure what this means, or how | |
257 | @var{integer} is interpreted. | |
258 | ||
259 | @item P | |
260 | Indicate this is a packed type, meaning that structure fields or array | |
261 | elements are placed more closely in memory, to save memory at the | |
262 | expense of speed. | |
168e8087 JK |
263 | |
264 | @item s@var{size} | |
265 | Size in bits of a variable of this type. This is fully supported by GDB | |
266 | 4.11 and later. | |
267 | ||
268 | @item S | |
269 | Indicate that this type is a string instead of an array of characters, | |
270 | or a bitstring instead of a set. It doesn't change the layout of the | |
271 | data being represented, but does enable the debugger to know which type | |
272 | it is. | |
6897f9ec JK |
273 | @end table |
274 | ||
ae701604 JK |
275 | All of this can make the string field quite long. All versions of GDB, |
276 | and some versions of dbx, can handle arbitrarily long strings. But many | |
277 | versions of dbx (or assemblers or linkers, I'm not sure which) | |
278 | cretinously limit the strings to about 80 characters, so compilers which | |
279 | must work with such systems need to split the @code{.stabs} directive | |
280 | into several @code{.stabs} directives. Each stab duplicates every field | |
281 | except the string field. The string field of every stab except the last | |
282 | is marked as continued with a backslash at the end (in the assembly code | |
283 | this may be written as a double backslash, depending on the assembler). | |
284 | Removing the backslashes and concatenating the string fields of each | |
41d7671d JK |
285 | stab produces the original, long string. Just to be incompatible (or so |
286 | they don't have to worry about what the assembler does with | |
287 | backslashes), AIX can use @samp{?} instead of backslash. | |
e505224d | 288 | |
bf9d2537 DM |
289 | @node C Example |
290 | @section A Simple Example in C Source | |
e505224d PB |
291 | |
292 | To get the flavor of how stabs describe source information for a C | |
293 | program, let's look at the simple program: | |
294 | ||
295 | @example | |
6fe91f2c | 296 | main() |
e505224d | 297 | @{ |
139741da | 298 | printf("Hello world"); |
e505224d PB |
299 | @} |
300 | @end example | |
301 | ||
139741da RP |
302 | When compiled with @samp{-g}, the program above yields the following |
303 | @file{.s} file. Line numbers have been added to make it easier to refer | |
304 | to parts of the @file{.s} file in the description of the stabs that | |
305 | follows. | |
e505224d | 306 | |
bf9d2537 DM |
307 | @node Assembly Code |
308 | @section The Simple Example at the Assembly Level | |
e505224d | 309 | |
6fe91f2c DM |
310 | This simple ``hello world'' example demonstrates several of the stab |
311 | types used to describe C language source files. | |
312 | ||
e505224d PB |
313 | @example |
314 | 1 gcc2_compiled.: | |
315 | 2 .stabs "/cygint/s1/users/jcm/play/",100,0,0,Ltext0 | |
316 | 3 .stabs "hello.c",100,0,0,Ltext0 | |
317 | 4 .text | |
318 | 5 Ltext0: | |
319 | 6 .stabs "int:t1=r1;-2147483648;2147483647;",128,0,0,0 | |
320 | 7 .stabs "char:t2=r2;0;127;",128,0,0,0 | |
321 | 8 .stabs "long int:t3=r1;-2147483648;2147483647;",128,0,0,0 | |
322 | 9 .stabs "unsigned int:t4=r1;0;-1;",128,0,0,0 | |
323 | 10 .stabs "long unsigned int:t5=r1;0;-1;",128,0,0,0 | |
324 | 11 .stabs "short int:t6=r1;-32768;32767;",128,0,0,0 | |
325 | 12 .stabs "long long int:t7=r1;0;-1;",128,0,0,0 | |
326 | 13 .stabs "short unsigned int:t8=r1;0;65535;",128,0,0,0 | |
327 | 14 .stabs "long long unsigned int:t9=r1;0;-1;",128,0,0,0 | |
328 | 15 .stabs "signed char:t10=r1;-128;127;",128,0,0,0 | |
329 | 16 .stabs "unsigned char:t11=r1;0;255;",128,0,0,0 | |
330 | 17 .stabs "float:t12=r1;4;0;",128,0,0,0 | |
331 | 18 .stabs "double:t13=r1;8;0;",128,0,0,0 | |
332 | 19 .stabs "long double:t14=r1;8;0;",128,0,0,0 | |
333 | 20 .stabs "void:t15=15",128,0,0,0 | |
139741da | 334 | 21 .align 4 |
e505224d | 335 | 22 LC0: |
139741da RP |
336 | 23 .ascii "Hello, world!\12\0" |
337 | 24 .align 4 | |
338 | 25 .global _main | |
339 | 26 .proc 1 | |
e505224d PB |
340 | 27 _main: |
341 | 28 .stabn 68,0,4,LM1 | |
342 | 29 LM1: | |
139741da RP |
343 | 30 !#PROLOGUE# 0 |
344 | 31 save %sp,-136,%sp | |
345 | 32 !#PROLOGUE# 1 | |
346 | 33 call ___main,0 | |
347 | 34 nop | |
e505224d PB |
348 | 35 .stabn 68,0,5,LM2 |
349 | 36 LM2: | |
350 | 37 LBB2: | |
139741da RP |
351 | 38 sethi %hi(LC0),%o1 |
352 | 39 or %o1,%lo(LC0),%o0 | |
353 | 40 call _printf,0 | |
354 | 41 nop | |
e505224d PB |
355 | 42 .stabn 68,0,6,LM3 |
356 | 43 LM3: | |
357 | 44 LBE2: | |
358 | 45 .stabn 68,0,6,LM4 | |
359 | 46 LM4: | |
360 | 47 L1: | |
139741da RP |
361 | 48 ret |
362 | 49 restore | |
e505224d PB |
363 | 50 .stabs "main:F1",36,0,0,_main |
364 | 51 .stabn 192,0,0,LBB2 | |
365 | 52 .stabn 224,0,0,LBE2 | |
366 | @end example | |
367 | ||
bf9d2537 DM |
368 | @node Program Structure |
369 | @chapter Encoding the Structure of the Program | |
e505224d | 370 | |
685a5e86 DM |
371 | The elements of the program structure that stabs encode include the name |
372 | of the main function, the names of the source and include files, the | |
373 | line numbers, procedure names and types, and the beginnings and ends of | |
374 | blocks of code. | |
375 | ||
e505224d | 376 | @menu |
bf9d2537 DM |
377 | * Main Program:: Indicate what the main program is |
378 | * Source Files:: The path and name of the source file | |
379 | * Include Files:: Names of include files | |
380 | * Line Numbers:: | |
6fe91f2c | 381 | * Procedures:: |
bf9d2537 DM |
382 | * Nested Procedures:: |
383 | * Block Structure:: | |
e505224d PB |
384 | @end menu |
385 | ||
bf9d2537 DM |
386 | @node Main Program |
387 | @section Main Program | |
499a5faa | 388 | |
685a5e86 | 389 | @findex N_MAIN |
499a5faa | 390 | Most languages allow the main program to have any name. The |
685a5e86 | 391 | @code{N_MAIN} stab type tells the debugger the name that is used in this |
0a95c18c | 392 | program. Only the string field is significant; it is the name of |
685a5e86 DM |
393 | a function which is the main program. Most C compilers do not use this |
394 | stab (they expect the debugger to assume that the name is @code{main}), | |
395 | but some C compilers emit an @code{N_MAIN} stab for the @code{main} | |
396 | function. | |
499a5faa | 397 | |
bf9d2537 DM |
398 | @node Source Files |
399 | @section Paths and Names of the Source Files | |
e505224d | 400 | |
685a5e86 | 401 | @findex N_SO |
63cef7d7 JK |
402 | Before any other stabs occur, there must be a stab specifying the source |
403 | file. This information is contained in a symbol of stab type | |
0a95c18c JK |
404 | @code{N_SO}; the string field contains the name of the file. The |
405 | value of the symbol is the start address of the portion of the | |
685a5e86 | 406 | text section corresponding to that file. |
e505224d | 407 | |
0a95c18c | 408 | With the Sun Solaris2 compiler, the desc field contains a |
ded6bcab | 409 | source-language code. |
685a5e86 | 410 | @c Do the debuggers use it? What are the codes? -djm |
ded6bcab | 411 | |
6fe91f2c | 412 | Some compilers (for example, GCC2 and SunOS4 @file{/bin/cc}) also |
63cef7d7 JK |
413 | include the directory in which the source was compiled, in a second |
414 | @code{N_SO} symbol preceding the one containing the file name. This | |
ded6bcab | 415 | symbol can be distinguished by the fact that it ends in a slash. Code |
685a5e86 | 416 | from the @code{cfront} C++ compiler can have additional @code{N_SO} symbols for |
ded6bcab JK |
417 | nonexistent source files after the @code{N_SO} for the real source file; |
418 | these are believed to contain no useful information. | |
e505224d | 419 | |
63cef7d7 JK |
420 | For example: |
421 | ||
422 | @example | |
baf4ded0 | 423 | .stabs "/cygint/s1/users/jcm/play/",100,0,0,Ltext0 # @r{100 is N_SO} |
63cef7d7 JK |
424 | .stabs "hello.c",100,0,0,Ltext0 |
425 | .text | |
426 | Ltext0: | |
427 | @end example | |
428 | ||
429 | Instead of @code{N_SO} symbols, XCOFF uses a @code{.file} assembler | |
430 | directive which assembles to a standard COFF @code{.file} symbol; | |
431 | explaining this in detail is outside the scope of this document. | |
432 | ||
bf9d2537 DM |
433 | @node Include Files |
434 | @section Names of Include Files | |
6fe91f2c | 435 | |
685a5e86 | 436 | There are several schemes for dealing with include files: the |
6fe91f2c DM |
437 | traditional @code{N_SOL} approach, Sun's @code{N_BINCL} approach, and the |
438 | XCOFF @code{C_BINCL} approach (which despite the similar name has little in | |
63cef7d7 JK |
439 | common with @code{N_BINCL}). |
440 | ||
685a5e86 | 441 | @findex N_SOL |
63cef7d7 | 442 | An @code{N_SOL} symbol specifies which include file subsequent symbols |
f4548a46 JK |
443 | refer to. The string field is the name of the file and the value is the |
444 | text address corresponding to the end of the previous include file and | |
445 | the start of this one. To specify the main source file again, use an | |
446 | @code{N_SOL} symbol with the name of the main source file. | |
685a5e86 | 447 | |
685a5e86 DM |
448 | @findex N_BINCL |
449 | @findex N_EINCL | |
450 | @findex N_EXCL | |
43603088 JK |
451 | The @code{N_BINCL} approach works as follows. An @code{N_BINCL} symbol |
452 | specifies the start of an include file. In an object file, only the | |
0a95c18c | 453 | string is significant; the Sun linker puts data into some of the |
43603088 | 454 | other fields. The end of the include file is marked by an |
0a95c18c | 455 | @code{N_EINCL} symbol (which has no string field). In an object |
43603088 JK |
456 | file, there is no significant data in the @code{N_EINCL} symbol; the Sun |
457 | linker puts data into some of the fields. @code{N_BINCL} and | |
458 | @code{N_EINCL} can be nested. | |
459 | ||
460 | If the linker detects that two source files have identical stabs between | |
461 | an @code{N_BINCL} and @code{N_EINCL} pair (as will generally be the case | |
685a5e86 DM |
462 | for a header file), then it only puts out the stabs once. Each |
463 | additional occurance is replaced by an @code{N_EXCL} symbol. I believe | |
464 | the Sun (SunOS4, not sure about Solaris) linker is the only one which | |
465 | supports this feature. | |
466 | @c What do the fields of N_EXCL contain? -djm | |
685a5e86 | 467 | |
685a5e86 DM |
468 | @findex C_BINCL |
469 | @findex C_EINCL | |
63cef7d7 | 470 | For the start of an include file in XCOFF, use the @file{.bi} assembler |
6fe91f2c | 471 | directive, which generates a @code{C_BINCL} symbol. A @file{.ei} |
63cef7d7 JK |
472 | directive, which generates a @code{C_EINCL} symbol, denotes the end of |
473 | the include file. Both directives are followed by the name of the | |
0a95c18c JK |
474 | source file in quotes, which becomes the string for the symbol. |
475 | The value of each symbol, produced automatically by the assembler | |
685a5e86 DM |
476 | and linker, is the offset into the executable of the beginning |
477 | (inclusive, as you'd expect) or end (inclusive, as you would not expect) | |
478 | of the portion of the COFF line table that corresponds to this include | |
479 | file. @code{C_BINCL} and @code{C_EINCL} do not nest. | |
63cef7d7 | 480 | |
bf9d2537 DM |
481 | @node Line Numbers |
482 | @section Line Numbers | |
e505224d | 483 | |
685a5e86 DM |
484 | @findex N_SLINE |
485 | An @code{N_SLINE} symbol represents the start of a source line. The | |
ac31351a | 486 | desc field contains the line number and the value |
f0f4b04e | 487 | contains the code address for the start of that source line. On most |
e89d48dd JL |
488 | machines the address is absolute; for Sun's stabs-in-ELF and GNU's |
489 | stabs-in-SOM, it is relative to the function in which the @code{N_SLINE} | |
490 | symbol occurs. | |
e505224d | 491 | |
685a5e86 DM |
492 | @findex N_DSLINE |
493 | @findex N_BSLINE | |
63cef7d7 JK |
494 | GNU documents @code{N_DSLINE} and @code{N_BSLINE} symbols for line |
495 | numbers in the data or bss segments, respectively. They are identical | |
496 | to @code{N_SLINE} but are relocated differently by the linker. They | |
497 | were intended to be used to describe the source location of a variable | |
6fe91f2c | 498 | declaration, but I believe that GCC2 actually puts the line number in |
0a95c18c JK |
499 | the desc field of the stab for the variable itself. GDB has been |
500 | ignoring these symbols (unless they contain a string field) since | |
685a5e86 | 501 | at least GDB 3.5. |
139741da | 502 | |
63cef7d7 JK |
503 | For single source lines that generate discontiguous code, such as flow |
504 | of control statements, there may be more than one line number entry for | |
505 | the same source line. In this case there is a line number entry at the | |
506 | start of each code range, each with the same line number. | |
e505224d | 507 | |
56bfba9c JK |
508 | XCOFF does not use stabs for line numbers. Instead, it uses COFF line |
509 | numbers (which are outside the scope of this document). Standard COFF | |
510 | line numbers cannot deal with include files, but in XCOFF this is fixed | |
f19027a6 | 511 | with the @code{C_BINCL} method of marking include files (@pxref{Include |
408f6c34 | 512 | Files}). |
685a5e86 | 513 | |
899bafeb | 514 | @node Procedures |
6897f9ec JK |
515 | @section Procedures |
516 | ||
f19027a6 | 517 | @findex N_FUN, for functions |
43603088 JK |
518 | @findex N_FNAME |
519 | @findex N_STSYM, for functions (Sun acc) | |
520 | @findex N_GSYM, for functions (Sun acc) | |
521 | All of the following stabs normally use the @code{N_FUN} symbol type. | |
522 | However, Sun's @code{acc} compiler on SunOS4 uses @code{N_GSYM} and | |
523 | @code{N_STSYM}, which means that the value of the stab for the function | |
524 | is useless and the debugger must get the address of the function from | |
525 | the non-stab symbols instead. BSD Fortran is said to use @code{N_FNAME} | |
526 | with the same restriction; the value of the symbol is not useful (I'm | |
527 | not sure it really does use this, because GDB doesn't handle this and no | |
528 | one has complained). | |
6897f9ec | 529 | |
dd8126d9 | 530 | A function is represented by an @samp{F} symbol descriptor for a global |
43603088 | 531 | (extern) function, and @samp{f} for a static (local) function. The |
f8cbe518 JK |
532 | value is the address of the start of the function. For @code{a.out}, it |
533 | is already relocated. For stabs in ELF, the SunPRO compiler version | |
534 | 2.0.1 and GCC put out an address which gets relocated by the linker. In | |
535 | a future release SunPRO is planning to put out zero, in which case the | |
536 | address can be found from the ELF (non-stab) symbol. Because looking | |
537 | things up in the ELF symbols would probably be slow, I'm not sure how to | |
538 | find which symbol of that name is the right one, and this doesn't | |
539 | provide any way to deal with nested functions, it would probably be | |
540 | better to make the value of the stab an address relative to the start of | |
541 | the file. See @ref{Stabs In ELF} for more information on linker | |
542 | relocation of stabs in ELF files. | |
543 | ||
544 | The type information of the stab represents the return type of the | |
545 | function; thus @samp{foo:f5} means that foo is a function returning type | |
546 | 5. There is no need to try to get the line number of the start of the | |
547 | function from the stab for the function; it is in the next | |
43603088 JK |
548 | @code{N_SLINE} symbol. |
549 | ||
550 | @c FIXME: verify whether the "I suspect" below is true or not. | |
551 | Some compilers (such as Sun's Solaris compiler) support an extension for | |
552 | specifying the types of the arguments. I suspect this extension is not | |
553 | used for old (non-prototyped) function definitions in C. If the | |
554 | extension is in use, the type information of the stab for the function | |
555 | is followed by type information for each argument, with each argument | |
556 | preceded by @samp{;}. An argument type of 0 means that additional | |
557 | arguments are being passed, whose types and number may vary (@samp{...} | |
558 | in ANSI C). GDB has tolerated this extension (parsed the syntax, if not | |
559 | necessarily used the information) since at least version 4.8; I don't | |
560 | know whether all versions of dbx tolerate it. The argument types given | |
561 | here are not redundant with the symbols for the formal parameters | |
562 | (@pxref{Parameters}); they are the types of the arguments as they are | |
563 | passed, before any conversions might take place. For example, if a C | |
564 | function which is declared without a prototype takes a @code{float} | |
565 | argument, the value is passed as a @code{double} but then converted to a | |
566 | @code{float}. Debuggers need to use the types given in the arguments | |
567 | when printing values, but when calling the function they need to use the | |
568 | types given in the symbol defining the function. | |
ded6bcab JK |
569 | |
570 | If the return type and types of arguments of a function which is defined | |
6fe91f2c | 571 | in another source file are specified (i.e., a function prototype in ANSI |
ded6bcab JK |
572 | C), traditionally compilers emit no stab; the only way for the debugger |
573 | to find the information is if the source file where the function is | |
574 | defined was also compiled with debugging symbols. As an extension the | |
575 | Solaris compiler uses symbol descriptor @samp{P} followed by the return | |
576 | type of the function, followed by the arguments, each preceded by | |
577 | @samp{;}, as in a stab with symbol descriptor @samp{f} or @samp{F}. | |
578 | This use of symbol descriptor @samp{P} can be distinguished from its use | |
bf9d2537 | 579 | for register parameters (@pxref{Register Parameters}) by the fact that it has |
ded6bcab JK |
580 | symbol type @code{N_FUN}. |
581 | ||
6897f9ec JK |
582 | The AIX documentation also defines symbol descriptor @samp{J} as an |
583 | internal function. I assume this means a function nested within another | |
6fe91f2c | 584 | function. It also says symbol descriptor @samp{m} is a module in |
6897f9ec JK |
585 | Modula-2 or extended Pascal. |
586 | ||
587 | Procedures (functions which do not return values) are represented as | |
6fe91f2c DM |
588 | functions returning the @code{void} type in C. I don't see why this couldn't |
589 | be used for all languages (inventing a @code{void} type for this purpose if | |
6897f9ec JK |
590 | necessary), but the AIX documentation defines @samp{I}, @samp{P}, and |
591 | @samp{Q} for internal, global, and static procedures, respectively. | |
592 | These symbol descriptors are unusual in that they are not followed by | |
593 | type information. | |
594 | ||
43603088 JK |
595 | The following example shows a stab for a function @code{main} which |
596 | returns type number @code{1}. The @code{_main} specified for the value | |
597 | is a reference to an assembler label which is used to fill in the start | |
598 | address of the function. | |
685a5e86 DM |
599 | |
600 | @example | |
43603088 | 601 | .stabs "main:F1",36,0,0,_main # @r{36 is N_FUN} |
685a5e86 DM |
602 | @end example |
603 | ||
604 | The stab representing a procedure is located immediately following the | |
605 | code of the procedure. This stab is in turn directly followed by a | |
606 | group of other stabs describing elements of the procedure. These other | |
607 | stabs describe the procedure's parameters, its block local variables, and | |
608 | its block structure. | |
685a5e86 | 609 | |
bf9d2537 DM |
610 | @node Nested Procedures |
611 | @section Nested Procedures | |
685a5e86 | 612 | |
43603088 JK |
613 | For any of the symbol descriptors representing procedures, after the |
614 | symbol descriptor and the type information is optionally a scope | |
615 | specifier. This consists of a comma, the name of the procedure, another | |
616 | comma, and the name of the enclosing procedure. The first name is local | |
617 | to the scope specified, and seems to be redundant with the name of the | |
618 | symbol (before the @samp{:}). This feature is used by GCC, and | |
619 | presumably Pascal, Modula-2, etc., compilers, for nested functions. | |
6ea34847 JK |
620 | |
621 | If procedures are nested more than one level deep, only the immediately | |
685a5e86 | 622 | containing scope is specified. For example, this code: |
6ea34847 JK |
623 | |
624 | @example | |
625 | int | |
626 | foo (int x) | |
627 | @{ | |
628 | int bar (int y) | |
629 | @{ | |
630 | int baz (int z) | |
6fe91f2c DM |
631 | @{ |
632 | return x + y + z; | |
633 | @} | |
6ea34847 JK |
634 | return baz (x + 2 * y); |
635 | @} | |
636 | return x + bar (3 * x); | |
637 | @} | |
638 | @end example | |
639 | ||
640 | @noindent | |
641 | produces the stabs: | |
642 | ||
643 | @example | |
baf4ded0 | 644 | .stabs "baz:f1,baz,bar",36,0,0,_baz.15 # @r{36 is N_FUN} |
6ea34847 JK |
645 | .stabs "bar:f1,bar,foo",36,0,0,_bar.12 |
646 | .stabs "foo:F1",36,0,0,_foo | |
647 | @end example | |
6897f9ec | 648 | |
bf9d2537 DM |
649 | @node Block Structure |
650 | @section Block Structure | |
e505224d | 651 | |
685a5e86 DM |
652 | @findex N_LBRAC |
653 | @findex N_RBRAC | |
139741da | 654 | The program's block structure is represented by the @code{N_LBRAC} (left |
f0f4b04e | 655 | brace) and the @code{N_RBRAC} (right brace) stab types. The variables |
dd8126d9 | 656 | defined inside a block precede the @code{N_LBRAC} symbol for most |
f0f4b04e | 657 | compilers, including GCC. Other compilers, such as the Convex, Acorn |
f958d5cd | 658 | RISC machine, and Sun @code{acc} compilers, put the variables after the |
0a95c18c | 659 | @code{N_LBRAC} symbol. The values of the @code{N_LBRAC} and |
f0f4b04e JK |
660 | @code{N_RBRAC} symbols are the start and end addresses of the code of |
661 | the block, respectively. For most machines, they are relative to the | |
662 | starting address of this source file. For the Gould NP1, they are | |
e89d48dd JL |
663 | absolute. For Sun's stabs-in-ELF and GNU's stabs-in-SOM, they are relative |
664 | to the function in which they occur. | |
e505224d | 665 | |
139741da | 666 | The @code{N_LBRAC} and @code{N_RBRAC} stabs that describe the block |
f0f4b04e | 667 | scope of a procedure are located after the @code{N_FUN} stab that |
6fe91f2c | 668 | represents the procedure itself. |
e505224d | 669 | |
0a95c18c | 670 | Sun documents the desc field of @code{N_LBRAC} and |
f0f4b04e | 671 | @code{N_RBRAC} symbols as containing the nesting level of the block. |
0a95c18c | 672 | However, dbx seems to not care, and GCC always sets desc to |
f0f4b04e | 673 | zero. |
e505224d | 674 | |
6897f9ec JK |
675 | @node Constants |
676 | @chapter Constants | |
677 | ||
678 | The @samp{c} symbol descriptor indicates that this stab represents a | |
679 | constant. This symbol descriptor is an exception to the general rule | |
680 | that symbol descriptors are followed by type information. Instead, it | |
681 | is followed by @samp{=} and one of the following: | |
682 | ||
683 | @table @code | |
b273dc0f | 684 | @item b @var{value} |
6897f9ec JK |
685 | Boolean constant. @var{value} is a numeric value; I assume it is 0 for |
686 | false or 1 for true. | |
687 | ||
b273dc0f | 688 | @item c @var{value} |
6897f9ec JK |
689 | Character constant. @var{value} is the numeric value of the constant. |
690 | ||
b273dc0f JK |
691 | @item e @var{type-information} , @var{value} |
692 | Constant whose value can be represented as integral. | |
693 | @var{type-information} is the type of the constant, as it would appear | |
bf9d2537 | 694 | after a symbol descriptor (@pxref{String Field}). @var{value} is the |
b273dc0f JK |
695 | numeric value of the constant. GDB 4.9 does not actually get the right |
696 | value if @var{value} does not fit in a host @code{int}, but it does not | |
697 | do anything violent, and future debuggers could be extended to accept | |
698 | integers of any size (whether unsigned or not). This constant type is | |
699 | usually documented as being only for enumeration constants, but GDB has | |
700 | never imposed that restriction; I don't know about other debuggers. | |
701 | ||
702 | @item i @var{value} | |
703 | Integer constant. @var{value} is the numeric value. The type is some | |
704 | sort of generic integer type (for GDB, a host @code{int}); to specify | |
705 | the type explicitly, use @samp{e} instead. | |
706 | ||
707 | @item r @var{value} | |
6897f9ec JK |
708 | Real constant. @var{value} is the real value, which can be @samp{INF} |
709 | (optionally preceded by a sign) for infinity, @samp{QNAN} for a quiet | |
710 | NaN (not-a-number), or @samp{SNAN} for a signalling NaN. If it is a | |
711 | normal number the format is that accepted by the C library function | |
712 | @code{atof}. | |
713 | ||
b273dc0f | 714 | @item s @var{string} |
6897f9ec JK |
715 | String constant. @var{string} is a string enclosed in either @samp{'} |
716 | (in which case @samp{'} characters within the string are represented as | |
717 | @samp{\'} or @samp{"} (in which case @samp{"} characters within the | |
718 | string are represented as @samp{\"}). | |
719 | ||
b273dc0f | 720 | @item S @var{type-information} , @var{elements} , @var{bits} , @var{pattern} |
6897f9ec | 721 | Set constant. @var{type-information} is the type of the constant, as it |
bf9d2537 | 722 | would appear after a symbol descriptor (@pxref{String Field}). |
685a5e86 | 723 | @var{elements} is the number of elements in the set (does this means |
a03f27c3 JK |
724 | how many bits of @var{pattern} are actually used, which would be |
725 | redundant with the type, or perhaps the number of bits set in | |
726 | @var{pattern}? I don't get it), @var{bits} is the number of bits in the | |
727 | constant (meaning it specifies the length of @var{pattern}, I think), | |
728 | and @var{pattern} is a hexadecimal representation of the set. AIX | |
729 | documentation refers to a limit of 32 bytes, but I see no reason why | |
730 | this limit should exist. This form could probably be used for arbitrary | |
731 | constants, not just sets; the only catch is that @var{pattern} should be | |
732 | understood to be target, not host, byte order and format. | |
6897f9ec JK |
733 | @end table |
734 | ||
735 | The boolean, character, string, and set constants are not supported by | |
685a5e86 | 736 | GDB 4.9, but it ignores them. GDB 4.8 and earlier gave an error |
6897f9ec JK |
737 | message and refused to read symbols from the file containing the |
738 | constants. | |
739 | ||
685a5e86 | 740 | The above information is followed by @samp{;}. |
e505224d | 741 | |
899bafeb | 742 | @node Variables |
e505224d PB |
743 | @chapter Variables |
744 | ||
685a5e86 DM |
745 | Different types of stabs describe the various ways that variables can be |
746 | allocated: on the stack, globally, in registers, in common blocks, | |
747 | statically, or as arguments to a function. | |
748 | ||
e505224d | 749 | @menu |
bf9d2537 DM |
750 | * Stack Variables:: Variables allocated on the stack. |
751 | * Global Variables:: Variables used by more than one source file. | |
752 | * Register Variables:: Variables in registers. | |
753 | * Common Blocks:: Variables statically allocated together. | |
24dcc707 | 754 | * Statics:: Variables local to one source file. |
f19027a6 | 755 | * Based Variables:: Fortran pointer based variables. |
24dcc707 | 756 | * Parameters:: Variables for arguments to functions. |
e505224d PB |
757 | @end menu |
758 | ||
bf9d2537 DM |
759 | @node Stack Variables |
760 | @section Automatic Variables Allocated on the Stack | |
e505224d | 761 | |
685a5e86 DM |
762 | If a variable's scope is local to a function and its lifetime is only as |
763 | long as that function executes (C calls such variables | |
764 | @dfn{automatic}), it can be allocated in a register (@pxref{Register | |
bf9d2537 | 765 | Variables}) or on the stack. |
e505224d | 766 | |
685a5e86 | 767 | @findex N_LSYM |
43603088 JK |
768 | Each variable allocated on the stack has a stab with the symbol |
769 | descriptor omitted. Since type information should begin with a digit, | |
770 | @samp{-}, or @samp{(}, only those characters precluded from being used | |
771 | for symbol descriptors. However, the Acorn RISC machine (ARM) is said | |
772 | to get this wrong: it puts out a mere type definition here, without the | |
773 | preceding @samp{@var{type-number}=}. This is a bad idea; there is no | |
774 | guarantee that type descriptors are distinct from symbol descriptors. | |
775 | Stabs for stack variables use the @code{N_LSYM} stab type. | |
e505224d | 776 | |
0a95c18c | 777 | The value of the stab is the offset of the variable within the |
685a5e86 DM |
778 | local variables. On most machines this is an offset from the frame |
779 | pointer and is negative. The location of the stab specifies which block | |
bf9d2537 | 780 | it is defined in; see @ref{Block Structure}. |
e505224d | 781 | |
685a5e86 | 782 | For example, the following C code: |
e505224d | 783 | |
e7bb76cc JK |
784 | @example |
785 | int | |
786 | main () | |
787 | @{ | |
788 | int x; | |
789 | @} | |
790 | @end example | |
139741da | 791 | |
685a5e86 | 792 | produces the following stabs: |
e505224d | 793 | |
e7bb76cc | 794 | @example |
baf4ded0 JK |
795 | .stabs "main:F1",36,0,0,_main # @r{36 is N_FUN} |
796 | .stabs "x:1",128,0,0,-12 # @r{128 is N_LSYM} | |
797 | .stabn 192,0,0,LBB2 # @r{192 is N_LBRAC} | |
798 | .stabn 224,0,0,LBE2 # @r{224 is N_RBRAC} | |
e505224d PB |
799 | @end example |
800 | ||
685a5e86 | 801 | @xref{Procedures} for more information on the @code{N_FUN} stab, and |
bf9d2537 | 802 | @ref{Block Structure} for more information on the @code{N_LBRAC} and |
685a5e86 | 803 | @code{N_RBRAC} stabs. |
e505224d | 804 | |
bf9d2537 DM |
805 | @node Global Variables |
806 | @section Global Variables | |
e505224d | 807 | |
685a5e86 DM |
808 | @findex N_GSYM |
809 | A variable whose scope is not specific to just one source file is | |
baf4ded0 JK |
810 | represented by the @samp{G} symbol descriptor. These stabs use the |
811 | @code{N_GSYM} stab type. The type information for the stab | |
bf9d2537 | 812 | (@pxref{String Field}) gives the type of the variable. |
e505224d | 813 | |
baf4ded0 | 814 | For example, the following source code: |
6fe91f2c | 815 | |
e505224d | 816 | @example |
baf4ded0 | 817 | char g_foo = 'c'; |
e505224d PB |
818 | @end example |
819 | ||
139741da | 820 | @noindent |
baf4ded0 | 821 | yields the following assembly code: |
e505224d PB |
822 | |
823 | @example | |
baf4ded0 JK |
824 | .stabs "g_foo:G2",32,0,0,0 # @r{32 is N_GSYM} |
825 | .global _g_foo | |
826 | .data | |
827 | _g_foo: | |
828 | .byte 99 | |
e505224d PB |
829 | @end example |
830 | ||
baf4ded0 JK |
831 | The address of the variable represented by the @code{N_GSYM} is not |
832 | contained in the @code{N_GSYM} stab. The debugger gets this information | |
833 | from the external symbol for the global variable. In the example above, | |
834 | the @code{.global _g_foo} and @code{_g_foo:} lines tell the assembler to | |
835 | produce an external symbol. | |
e505224d | 836 | |
bf9d2537 DM |
837 | @node Register Variables |
838 | @section Register Variables | |
139741da | 839 | |
685a5e86 | 840 | @findex N_RSYM |
8c59ee11 JK |
841 | @c According to an old version of this manual, AIX uses C_RPSYM instead |
842 | @c of C_RSYM. I am skeptical; this should be verified. | |
6897f9ec | 843 | Register variables have their own stab type, @code{N_RSYM}, and their |
ac31351a | 844 | own symbol descriptor, @samp{r}. The stab's value is the |
6897f9ec | 845 | number of the register where the variable data will be stored. |
685a5e86 | 846 | @c .stabs "name:type",N_RSYM,0,RegSize,RegNumber (Sun doc) |
e505224d | 847 | |
6897f9ec | 848 | AIX defines a separate symbol descriptor @samp{d} for floating point |
935d305d | 849 | registers. This seems unnecessary; why not just just give floating |
807e8368 JK |
850 | point registers different register numbers? I have not verified whether |
851 | the compiler actually uses @samp{d}. | |
e505224d | 852 | |
6897f9ec | 853 | If the register is explicitly allocated to a global variable, but not |
685a5e86 | 854 | initialized, as in: |
e505224d PB |
855 | |
856 | @example | |
6897f9ec | 857 | register int g_bar asm ("%g5"); |
e505224d PB |
858 | @end example |
859 | ||
685a5e86 DM |
860 | @noindent |
861 | then the stab may be emitted at the end of the object file, with | |
6897f9ec | 862 | the other bss symbols. |
e505224d | 863 | |
bf9d2537 DM |
864 | @node Common Blocks |
865 | @section Common Blocks | |
807e8368 JK |
866 | |
867 | A common block is a statically allocated section of memory which can be | |
868 | referred to by several source files. It may contain several variables. | |
685a5e86 DM |
869 | I believe Fortran is the only language with this feature. |
870 | ||
685a5e86 DM |
871 | @findex N_BCOMM |
872 | @findex N_ECOMM | |
05238df4 JK |
873 | @findex C_BCOMM |
874 | @findex C_ECOMM | |
685a5e86 DM |
875 | A @code{N_BCOMM} stab begins a common block and an @code{N_ECOMM} stab |
876 | ends it. The only field that is significant in these two stabs is the | |
0a95c18c | 877 | string, which names a normal (non-debugging) symbol that gives the |
05238df4 JK |
878 | address of the common block. According to IBM documentation, only the |
879 | @code{N_BCOMM} has the name of the common block (even though their | |
880 | compiler actually puts it both places). | |
685a5e86 | 881 | |
685a5e86 | 882 | @findex N_ECOML |
05238df4 JK |
883 | @findex C_ECOML |
884 | The stabs for the members of the common block are between the | |
885 | @code{N_BCOMM} and the @code{N_ECOMM}; the value of each stab is the | |
886 | offset within the common block of that variable. IBM uses the | |
887 | @code{C_ECOML} stab type, and there is a corresponding @code{N_ECOML} | |
888 | stab type, but Sun's Fortran compiler uses @code{N_GSYM} instead. The | |
889 | variables within a common block use the @samp{V} symbol descriptor (I | |
890 | believe this is true of all Fortran variables). Other stabs (at least | |
891 | type declarations using @code{C_DECL}) can also be between the | |
892 | @code{N_BCOMM} and the @code{N_ECOMM}. | |
807e8368 | 893 | |
24dcc707 | 894 | @node Statics |
bf9d2537 | 895 | @section Static Variables |
e505224d | 896 | |
24dcc707 JK |
897 | Initialized static variables are represented by the @samp{S} and |
898 | @samp{V} symbol descriptors. @samp{S} means file scope static, and | |
8f85a435 JK |
899 | @samp{V} means procedure scope static. One exception: in XCOFF, IBM's |
900 | xlc compiler always uses @samp{V}, and whether it is file scope or not | |
901 | is distinguished by whether the stab is located within a function. | |
e505224d | 902 | |
935d305d JK |
903 | @c This is probably not worth mentioning; it is only true on the sparc |
904 | @c for `double' variables which although declared const are actually in | |
905 | @c the data segment (the text segment can't guarantee 8 byte alignment). | |
6fe91f2c | 906 | @c (although GCC |
dd8126d9 | 907 | @c 2.4.5 has a bug in that it uses @code{N_FUN}, so neither dbx nor GDB can |
935d305d | 908 | @c find the variables) |
685a5e86 DM |
909 | @findex N_STSYM |
910 | @findex N_LCSYM | |
f19027a6 JK |
911 | @findex N_FUN, for variables |
912 | @findex N_ROSYM | |
31a932d8 JK |
913 | In a.out files, @code{N_STSYM} means the data section, @code{N_FUN} |
914 | means the text section, and @code{N_LCSYM} means the bss section. For | |
915 | those systems with a read-only data section separate from the text | |
916 | section (Solaris), @code{N_ROSYM} means the read-only data section. | |
e505224d | 917 | |
685a5e86 | 918 | For example, the source lines: |
e505224d PB |
919 | |
920 | @example | |
24dcc707 JK |
921 | static const int var_const = 5; |
922 | static int var_init = 2; | |
923 | static int var_noinit; | |
e505224d PB |
924 | @end example |
925 | ||
24dcc707 JK |
926 | @noindent |
927 | yield the following stabs: | |
e505224d PB |
928 | |
929 | @example | |
baf4ded0 | 930 | .stabs "var_const:S1",36,0,0,_var_const # @r{36 is N_FUN} |
685a5e86 | 931 | @dots{} |
baf4ded0 | 932 | .stabs "var_init:S1",38,0,0,_var_init # @r{38 is N_STSYM} |
685a5e86 | 933 | @dots{} |
baf4ded0 | 934 | .stabs "var_noinit:S1",40,0,0,_var_noinit # @r{40 is N_LCSYM} |
e505224d | 935 | @end example |
685a5e86 | 936 | |
8f85a435 JK |
937 | In XCOFF files, the stab type need not indicate the section; |
938 | @code{C_STSYM} can be used for all statics. Also, each static variable | |
939 | is enclosed in a static block. A @code{C_BSTAT} (emitted with a | |
940 | @samp{.bs} assembler directive) symbol begins the static block; its | |
941 | value is the address of the static block, its section is the section of | |
942 | the variables in that static block, and its name is @samp{.bs}. A | |
943 | @code{C_ESTAT} (emitted with a @samp{.es} assembler directive) symbol | |
944 | ends the static block; its name is @samp{.es} and its value and section | |
945 | are ignored. | |
685a5e86 DM |
946 | |
947 | In ECOFF files, the storage class is used to specify the section, so the | |
31a932d8 | 948 | stab type need not indicate the section. |
685a5e86 | 949 | |
f8cbe518 JK |
950 | In ELF files, for the SunPRO compiler version 2.0.1, symbol descriptor |
951 | @samp{S} means that the address is absolute (the linker relocates it) | |
952 | and symbol descriptor @samp{V} means that the address is relative to the | |
953 | start of the relevant section for that compilation unit. SunPRO has | |
954 | plans to have the linker stop relocating stabs; I suspect that their the | |
955 | debugger gets the address from the corresponding ELF (not stab) symbol. | |
956 | I'm not sure how to find which symbol of that name is the right one. | |
957 | The clean way to do all this would be to have a the value of a symbol | |
958 | descriptor @samp{S} symbol be an offset relative to the start of the | |
959 | file, just like everything else, but that introduces obvious | |
960 | compatibility problems. For more information on linker stab relocation, | |
961 | @xref{Stabs In ELF}. | |
e505224d | 962 | |
f19027a6 JK |
963 | @node Based Variables |
964 | @section Fortran Based Variables | |
965 | ||
966 | Fortran (at least, the Sun and SGI dialects of FORTRAN-77) has a feature | |
967 | which allows allocating arrays with @code{malloc}, but which avoids | |
968 | blurring the line between arrays and pointers the way that C does. In | |
969 | stabs such a variable uses the @samp{b} symbol descriptor. | |
970 | ||
971 | For example, the Fortran declarations | |
972 | ||
973 | @example | |
974 | real foo, foo10(10), foo10_5(10,5) | |
975 | pointer (foop, foo) | |
976 | pointer (foo10p, foo10) | |
977 | pointer (foo105p, foo10_5) | |
978 | @end example | |
979 | ||
980 | produce the stabs | |
981 | ||
982 | @example | |
983 | foo:b6 | |
984 | foo10:bar3;1;10;6 | |
985 | foo10_5:bar3;1;5;ar3;1;10;6 | |
986 | @end example | |
987 | ||
988 | In this example, @code{real} is type 6 and type 3 is an integral type | |
989 | which is the type of the subscripts of the array (probably | |
990 | @code{integer}). | |
991 | ||
992 | The @samp{b} symbol descriptor is like @samp{V} in that it denotes a | |
993 | statically allocated symbol whose scope is local to a function; see | |
994 | @xref{Statics}. The value of the symbol, instead of being the address | |
995 | of the variable itself, is the address of a pointer to that variable. | |
996 | So in the above example, the value of the @code{foo} stab is the address | |
997 | of a pointer to a real, the value of the @code{foo10} stab is the | |
998 | address of a pointer to a 10-element array of reals, and the value of | |
999 | the @code{foo10_5} stab is the address of a pointer to a 5-element array | |
1000 | of 10-element arrays of reals. | |
1001 | ||
899bafeb | 1002 | @node Parameters |
907a9cab JK |
1003 | @section Parameters |
1004 | ||
43603088 | 1005 | Formal parameters to a function are represented by a stab (or sometimes |
685a5e86 DM |
1006 | two; see below) for each parameter. The stabs are in the order in which |
1007 | the debugger should print the parameters (i.e., the order in which the | |
dd8126d9 JK |
1008 | parameters are declared in the source file). The exact form of the stab |
1009 | depends on how the parameter is being passed. | |
e505224d | 1010 | |
685a5e86 DM |
1011 | @findex N_PSYM |
1012 | Parameters passed on the stack use the symbol descriptor @samp{p} and | |
0a95c18c | 1013 | the @code{N_PSYM} symbol type. The value of the symbol is an offset |
dd8126d9 | 1014 | used to locate the parameter on the stack; its exact meaning is |
685a5e86 | 1015 | machine-dependent, but on most machines it is an offset from the frame |
dd8126d9 | 1016 | pointer. |
b82ea042 | 1017 | |
685a5e86 DM |
1018 | As a simple example, the code: |
1019 | ||
1020 | @example | |
1021 | main (argc, argv) | |
1022 | int argc; | |
1023 | char **argv; | |
1024 | @end example | |
1025 | ||
1026 | produces the stabs: | |
1027 | ||
1028 | @example | |
1029 | .stabs "main:F1",36,0,0,_main # @r{36 is N_FUN} | |
1030 | .stabs "argc:p1",160,0,0,68 # @r{160 is N_PSYM} | |
1031 | .stabs "argv:p20=*21=*2",160,0,0,72 | |
1032 | @end example | |
1033 | ||
1034 | The type definition of @code{argv} is interesting because it contains | |
1035 | several type definitions. Type 21 is pointer to type 2 (char) and | |
1036 | @code{argv} (type 20) is pointer to type 21. | |
43603088 JK |
1037 | |
1038 | @c FIXME: figure out what these mean and describe them coherently. | |
408f6c34 JK |
1039 | The following symbol descriptors are also said to go with @code{N_PSYM}. |
1040 | The value of the symbol is said to be an offset from the argument | |
1041 | pointer (I'm not sure whether this is true or not). | |
43603088 JK |
1042 | |
1043 | @example | |
408f6c34 JK |
1044 | pP (<<??>>) |
1045 | pF Fortran function parameter | |
1046 | X (function result variable) | |
43603088 | 1047 | @end example |
685a5e86 DM |
1048 | |
1049 | @menu | |
bf9d2537 DM |
1050 | * Register Parameters:: |
1051 | * Local Variable Parameters:: | |
1052 | * Reference Parameters:: | |
1053 | * Conformant Arrays:: | |
685a5e86 DM |
1054 | @end menu |
1055 | ||
bf9d2537 DM |
1056 | @node Register Parameters |
1057 | @subsection Passing Parameters in Registers | |
685a5e86 DM |
1058 | |
1059 | If the parameter is passed in a register, then traditionally there are | |
1060 | two symbols for each argument: | |
e505224d PB |
1061 | |
1062 | @example | |
baf4ded0 JK |
1063 | .stabs "arg:p1" . . . ; N_PSYM |
1064 | .stabs "arg:r1" . . . ; N_RSYM | |
e505224d PB |
1065 | @end example |
1066 | ||
685a5e86 DM |
1067 | Debuggers use the second one to find the value, and the first one to |
1068 | know that it is an argument. | |
1069 | ||
685a5e86 | 1070 | @findex C_RPSYM |
43603088 | 1071 | @findex N_RSYM, for parameters |
685a5e86 DM |
1072 | Because that approach is kind of ugly, some compilers use symbol |
1073 | descriptor @samp{P} or @samp{R} to indicate an argument which is in a | |
1074 | register. Symbol type @code{C_RPSYM} is used with @samp{R} and | |
ac31351a | 1075 | @code{N_RSYM} is used with @samp{P}. The symbol's value is |
685a5e86 DM |
1076 | the register number. @samp{P} and @samp{R} mean the same thing; the |
1077 | difference is that @samp{P} is a GNU invention and @samp{R} is an IBM | |
1078 | (XCOFF) invention. As of version 4.9, GDB should handle either one. | |
e505224d | 1079 | |
685a5e86 DM |
1080 | There is at least one case where GCC uses a @samp{p} and @samp{r} pair |
1081 | rather than @samp{P}; this is where the argument is passed in the | |
1082 | argument list and then loaded into a register. | |
b82ea042 | 1083 | |
685a5e86 | 1084 | According to the AIX documentation, symbol descriptor @samp{D} is for a |
acf7d010 JK |
1085 | parameter passed in a floating point register. This seems |
1086 | unnecessary---why not just use @samp{R} with a register number which | |
23aed449 | 1087 | indicates that it's a floating point register? I haven't verified |
6897f9ec JK |
1088 | whether the system actually does what the documentation indicates. |
1089 | ||
43603088 JK |
1090 | @c FIXME: On the hppa this is for any type > 8 bytes, I think, and not |
1091 | @c for small structures (investigate). | |
c156f3c1 JK |
1092 | On the sparc and hppa, for a @samp{P} symbol whose type is a structure |
1093 | or union, the register contains the address of the structure. On the | |
685a5e86 DM |
1094 | sparc, this is also true of a @samp{p} and @samp{r} pair (using Sun |
1095 | @code{cc}) or a @samp{p} symbol. However, if a (small) structure is | |
1096 | really in a register, @samp{r} is used. And, to top it all off, on the | |
1097 | hppa it might be a structure which was passed on the stack and loaded | |
1098 | into a register and for which there is a @samp{p} and @samp{r} pair! I | |
1099 | believe that symbol descriptor @samp{i} is supposed to deal with this | |
1100 | case (it is said to mean "value parameter by reference, indirect | |
1101 | access"; I don't know the source for this information), but I don't know | |
1102 | details or what compilers or debuggers use it, if any (not GDB or GCC). | |
1103 | It is not clear to me whether this case needs to be dealt with | |
bf9d2537 | 1104 | differently than parameters passed by reference (@pxref{Reference Parameters}). |
685a5e86 | 1105 | |
bf9d2537 DM |
1106 | @node Local Variable Parameters |
1107 | @subsection Storing Parameters as Local Variables | |
685a5e86 DM |
1108 | |
1109 | There is a case similar to an argument in a register, which is an | |
1110 | argument that is actually stored as a local variable. Sometimes this | |
98ef6f31 JK |
1111 | happens when the argument was passed in a register and then the compiler |
1112 | stores it as a local variable. If possible, the compiler should claim | |
685a5e86 DM |
1113 | that it's in a register, but this isn't always done. |
1114 | ||
9ab86fa3 JK |
1115 | If a parameter is passed as one type and converted to a smaller type by |
1116 | the prologue (for example, the parameter is declared as a @code{float}, | |
1117 | but the calling conventions specify that it is passed as a | |
1118 | @code{double}), then GCC2 (sometimes) uses a pair of symbols. The first | |
1119 | symbol uses symbol descriptor @samp{p} and the type which is passed. | |
1120 | The second symbol has the type and location which the parameter actually | |
1121 | has after the prologue. For example, suppose the following C code | |
1122 | appears with no prototypes involved: | |
1123 | ||
1124 | @example | |
1125 | void | |
1126 | subr (f) | |
1127 | float f; | |
1128 | @{ | |
1129 | @end example | |
f3bb0be2 | 1130 | |
e2525986 JK |
1131 | if @code{f} is passed as a double at stack offset 8, and the prologue |
1132 | converts it to a float in register number 0, then the stabs look like: | |
9ab86fa3 | 1133 | |
9ab86fa3 | 1134 | @example |
e2525986 JK |
1135 | .stabs "f:p13",160,0,3,8 # @r{160 is @code{N_PSYM}, here 13 is @code{double}} |
1136 | .stabs "f:r12",64,0,3,0 # @r{64 is @code{N_RSYM}, here 12 is @code{float}} | |
9ab86fa3 JK |
1137 | @end example |
1138 | ||
e2525986 JK |
1139 | In both stabs 3 is the line number where @code{f} is declared |
1140 | (@pxref{Line Numbers}). | |
1141 | ||
9ab86fa3 | 1142 | @findex N_LSYM, for parameter |
f3bb0be2 JK |
1143 | GCC, at least on the 960, has another solution to the same problem. It |
1144 | uses a single @samp{p} symbol descriptor for an argument which is stored | |
1145 | as a local variable but uses @code{N_LSYM} instead of @code{N_PSYM}. In | |
1146 | this case, the value of the symbol is an offset relative to the local | |
1147 | variables for that function, not relative to the arguments; on some | |
1148 | machines those are the same thing, but not on all. | |
1149 | ||
1150 | @c This is mostly just background info; the part that logically belongs | |
1151 | @c here is the last sentence. | |
1152 | On the VAX or on other machines in which the calling convention includes | |
1153 | the number of words of arguments actually passed, the debugger (GDB at | |
1154 | least) uses the parameter symbols to keep track of whether it needs to | |
1155 | print nameless arguments in addition to the formal parameters which it | |
1156 | has printed because each one has a stab. For example, in | |
1157 | ||
1158 | @example | |
1159 | extern int fprintf (FILE *stream, char *format, @dots{}); | |
1160 | @dots{} | |
1161 | fprintf (stdout, "%d\n", x); | |
1162 | @end example | |
1163 | ||
1164 | there are stabs for @code{stream} and @code{format}. On most machines, | |
1165 | the debugger can only print those two arguments (because it has no way | |
1166 | of knowing that additional arguments were passed), but on the VAX or | |
1167 | other machines with a calling convention which indicates the number of | |
1168 | words of arguments, the debugger can print all three arguments. To do | |
1169 | so, the parameter symbol (symbol descriptor @samp{p}) (not necessarily | |
1170 | @samp{r} or symbol descriptor omitted symbols) needs to contain the | |
1171 | actual type as passed (for example, @code{double} not @code{float} if it | |
1172 | is passed as a double and converted to a float). | |
685a5e86 | 1173 | |
bf9d2537 DM |
1174 | @node Reference Parameters |
1175 | @subsection Passing Parameters by Reference | |
685a5e86 DM |
1176 | |
1177 | If the parameter is passed by reference (e.g., Pascal @code{VAR} | |
1178 | parameters), then the symbol descriptor is @samp{v} if it is in the | |
1179 | argument list, or @samp{a} if it in a register. Other than the fact | |
1180 | that these contain the address of the parameter rather than the | |
1181 | parameter itself, they are identical to @samp{p} and @samp{R}, | |
1182 | respectively. I believe @samp{a} is an AIX invention; @samp{v} is | |
1183 | supported by all stabs-using systems as far as I know. | |
1184 | ||
bf9d2537 DM |
1185 | @node Conformant Arrays |
1186 | @subsection Passing Conformant Array Parameters | |
6897f9ec JK |
1187 | |
1188 | @c Is this paragraph correct? It is based on piecing together patchy | |
1189 | @c information and some guesswork | |
685a5e86 | 1190 | Conformant arrays are a feature of Modula-2, and perhaps other |
6897f9ec | 1191 | languages, in which the size of an array parameter is not known to the |
685a5e86 | 1192 | called function until run-time. Such parameters have two stabs: a |
6897f9ec | 1193 | @samp{x} for the array itself, and a @samp{C}, which represents the size |
0a95c18c | 1194 | of the array. The value of the @samp{x} stab is the offset in the |
6897f9ec | 1195 | argument list where the address of the array is stored (it this right? |
0a95c18c | 1196 | it is a guess); the value of the @samp{C} stab is the offset in the |
6897f9ec JK |
1197 | argument list where the size of the array (in elements? in bytes?) is |
1198 | stored. | |
1199 | ||
8c59ee11 | 1200 | @node Types |
bf9d2537 | 1201 | @chapter Defining Types |
e505224d | 1202 | |
685a5e86 DM |
1203 | The examples so far have described types as references to previously |
1204 | defined types, or defined in terms of subranges of or pointers to | |
1205 | previously defined types. This chapter describes the other type | |
1206 | descriptors that may follow the @samp{=} in a type definition. | |
e505224d PB |
1207 | |
1208 | @menu | |
bf9d2537 DM |
1209 | * Builtin Types:: Integers, floating point, void, etc. |
1210 | * Miscellaneous Types:: Pointers, sets, files, etc. | |
1211 | * Cross-References:: Referring to a type not yet defined. | |
8c59ee11 JK |
1212 | * Subranges:: A type with a specific range. |
1213 | * Arrays:: An aggregate type of same-typed elements. | |
1214 | * Strings:: Like an array but also has a length. | |
1215 | * Enumerations:: Like an integer but the values have names. | |
1216 | * Structures:: An aggregate type of different-typed elements. | |
ded6bcab JK |
1217 | * Typedefs:: Giving a type a name. |
1218 | * Unions:: Different types sharing storage. | |
bf9d2537 | 1219 | * Function Types:: |
e505224d PB |
1220 | @end menu |
1221 | ||
bf9d2537 DM |
1222 | @node Builtin Types |
1223 | @section Builtin Types | |
e505224d | 1224 | |
8c59ee11 JK |
1225 | Certain types are built in (@code{int}, @code{short}, @code{void}, |
1226 | @code{float}, etc.); the debugger recognizes these types and knows how | |
685a5e86 | 1227 | to handle them. Thus, don't be surprised if some of the following ways |
8c59ee11 JK |
1228 | of specifying builtin types do not specify everything that a debugger |
1229 | would need to know about the type---in some cases they merely specify | |
1230 | enough information to distinguish the type from other types. | |
1231 | ||
1232 | The traditional way to define builtin types is convolunted, so new ways | |
dd8126d9 JK |
1233 | have been invented to describe them. Sun's @code{acc} uses special |
1234 | builtin type descriptors (@samp{b} and @samp{R}), and IBM uses negative | |
685a5e86 | 1235 | type numbers. GDB accepts all three ways, as of version 4.8; dbx just |
dd8126d9 JK |
1236 | accepts the traditional builtin types and perhaps one of the other two |
1237 | formats. The following sections describe each of these formats. | |
8c59ee11 JK |
1238 | |
1239 | @menu | |
bf9d2537 DM |
1240 | * Traditional Builtin Types:: Put on your seatbelts and prepare for kludgery |
1241 | * Builtin Type Descriptors:: Builtin types with special type descriptors | |
1242 | * Negative Type Numbers:: Builtin types using negative type numbers | |
8c59ee11 JK |
1243 | @end menu |
1244 | ||
bf9d2537 DM |
1245 | @node Traditional Builtin Types |
1246 | @subsection Traditional Builtin Types | |
8c59ee11 | 1247 | |
685a5e86 DM |
1248 | This is the traditional, convoluted method for defining builtin types. |
1249 | There are several classes of such type definitions: integer, floating | |
1250 | point, and @code{void}. | |
1251 | ||
1252 | @menu | |
bf9d2537 DM |
1253 | * Traditional Integer Types:: |
1254 | * Traditional Other Types:: | |
685a5e86 DM |
1255 | @end menu |
1256 | ||
bf9d2537 DM |
1257 | @node Traditional Integer Types |
1258 | @subsubsection Traditional Integer Types | |
685a5e86 DM |
1259 | |
1260 | Often types are defined as subranges of themselves. If the bounding values | |
1261 | fit within an @code{int}, then they are given normally. For example: | |
8c59ee11 JK |
1262 | |
1263 | @example | |
baf4ded0 | 1264 | .stabs "int:t1=r1;-2147483648;2147483647;",128,0,0,0 # @r{128 is N_LSYM} |
8c59ee11 JK |
1265 | .stabs "char:t2=r2;0;127;",128,0,0,0 |
1266 | @end example | |
1267 | ||
1268 | Builtin types can also be described as subranges of @code{int}: | |
1269 | ||
1270 | @example | |
1271 | .stabs "unsigned short:t6=r1;0;65535;",128,0,0,0 | |
1272 | @end example | |
1273 | ||
685a5e86 DM |
1274 | If the lower bound of a subrange is 0 and the upper bound is -1, |
1275 | the type is an unsigned integral type whose bounds are too | |
1276 | big to describe in an @code{int}. Traditionally this is only used for | |
1277 | @code{unsigned int} and @code{unsigned long}: | |
8c59ee11 JK |
1278 | |
1279 | @example | |
1280 | .stabs "unsigned int:t4=r1;0;-1;",128,0,0,0 | |
8c59ee11 JK |
1281 | @end example |
1282 | ||
f8cbe518 JK |
1283 | For larger types, GCC 2.4.5 puts out bounds in octal, with one or more |
1284 | leading zeroes. In this case a negative bound consists of a number | |
1285 | which is a 1 bit (for the sign bit) followed by a 0 bit for each bit in | |
1286 | the number (except the sign bit), and a positive bound is one which is a | |
1287 | 1 bit for each bit in the number (except possibly the sign bit). All | |
1288 | known versions of dbx and GDB version 4 accept this (at least in the | |
1289 | sense of not refusing to process the file), but GDB 3.5 refuses to read | |
1290 | the whole file containing such symbols. So GCC 2.3.3 did not output the | |
1291 | proper size for these types. As an example of octal bounds, the string | |
1292 | fields of the stabs for 64 bit integer types look like: | |
1293 | ||
1294 | @c .stabs directives, etc., omitted to make it fit on the page. | |
1295 | @example | |
1296 | long int:t3=r1;001000000000000000000000;000777777777777777777777; | |
1297 | long unsigned int:t5=r1;000000000000000000000000;001777777777777777777777; | |
1298 | @end example | |
685a5e86 | 1299 | |
b273dc0f | 1300 | If the lower bound of a subrange is 0 and the upper bound is negative, |
685a5e86 | 1301 | the type is an unsigned integral type whose size in bytes is the |
b273dc0f JK |
1302 | absolute value of the upper bound. I believe this is a Convex |
1303 | convention for @code{unsigned long long}. | |
1304 | ||
1305 | If the lower bound of a subrange is negative and the upper bound is 0, | |
685a5e86 | 1306 | the type is a signed integral type whose size in bytes is |
b273dc0f JK |
1307 | the absolute value of the lower bound. I believe this is a Convex |
1308 | convention for @code{long long}. To distinguish this from a legitimate | |
1309 | subrange, the type should be a subrange of itself. I'm not sure whether | |
1310 | this is the case for Convex. | |
1311 | ||
bf9d2537 DM |
1312 | @node Traditional Other Types |
1313 | @subsubsection Traditional Other Types | |
685a5e86 DM |
1314 | |
1315 | If the upper bound of a subrange is 0 and the lower bound is positive, | |
1316 | the type is a floating point type, and the lower bound of the subrange | |
1317 | indicates the number of bytes in the type: | |
8c59ee11 JK |
1318 | |
1319 | @example | |
1320 | .stabs "float:t12=r1;4;0;",128,0,0,0 | |
1321 | .stabs "double:t13=r1;8;0;",128,0,0,0 | |
1322 | @end example | |
1323 | ||
1324 | However, GCC writes @code{long double} the same way it writes | |
dd8126d9 | 1325 | @code{double}, so there is no way to distinguish. |
8c59ee11 JK |
1326 | |
1327 | @example | |
1328 | .stabs "long double:t14=r1;8;0;",128,0,0,0 | |
1329 | @end example | |
1330 | ||
dd8126d9 JK |
1331 | Complex types are defined the same way as floating-point types; there is |
1332 | no way to distinguish a single-precision complex from a double-precision | |
1333 | floating-point type. | |
8c59ee11 JK |
1334 | |
1335 | The C @code{void} type is defined as itself: | |
1336 | ||
1337 | @example | |
1338 | .stabs "void:t15=15",128,0,0,0 | |
1339 | @end example | |
1340 | ||
1341 | I'm not sure how a boolean type is represented. | |
1342 | ||
bf9d2537 DM |
1343 | @node Builtin Type Descriptors |
1344 | @subsection Defining Builtin Types Using Builtin Type Descriptors | |
8c59ee11 | 1345 | |
685a5e86 DM |
1346 | This is the method used by Sun's @code{acc} for defining builtin types. |
1347 | These are the type descriptors to define builtin types: | |
8c59ee11 JK |
1348 | |
1349 | @table @code | |
1a8b5668 JK |
1350 | @c FIXME: clean up description of width and offset, once we figure out |
1351 | @c what they mean | |
8c59ee11 JK |
1352 | @item b @var{signed} @var{char-flag} @var{width} ; @var{offset} ; @var{nbits} ; |
1353 | Define an integral type. @var{signed} is @samp{u} for unsigned or | |
1354 | @samp{s} for signed. @var{char-flag} is @samp{c} which indicates this | |
1355 | is a character type, or is omitted. I assume this is to distinguish an | |
1356 | integral type from a character type of the same size, for example it | |
1357 | might make sense to set it for the C type @code{wchar_t} so the debugger | |
1358 | can print such variables differently (Solaris does not do this). Sun | |
1359 | sets it on the C types @code{signed char} and @code{unsigned char} which | |
1360 | arguably is wrong. @var{width} and @var{offset} appear to be for small | |
1361 | objects stored in larger ones, for example a @code{short} in an | |
1362 | @code{int} register. @var{width} is normally the number of bytes in the | |
1363 | type. @var{offset} seems to always be zero. @var{nbits} is the number | |
1364 | of bits in the type. | |
1365 | ||
1366 | Note that type descriptor @samp{b} used for builtin types conflicts with | |
bf9d2537 | 1367 | its use for Pascal space types (@pxref{Miscellaneous Types}); they can |
8c59ee11 JK |
1368 | be distinguished because the character following the type descriptor |
1369 | will be a digit, @samp{(}, or @samp{-} for a Pascal space type, or | |
1370 | @samp{u} or @samp{s} for a builtin type. | |
1371 | ||
1372 | @item w | |
1373 | Documented by AIX to define a wide character type, but their compiler | |
bf9d2537 | 1374 | actually uses negative type numbers (@pxref{Negative Type Numbers}). |
8c59ee11 | 1375 | |
685a5e86 DM |
1376 | @item R @var{fp-type} ; @var{bytes} ; |
1377 | Define a floating point type. @var{fp-type} has one of the following values: | |
1a8b5668 JK |
1378 | |
1379 | @table @code | |
1380 | @item 1 (NF_SINGLE) | |
1381 | IEEE 32-bit (single precision) floating point format. | |
1382 | ||
1383 | @item 2 (NF_DOUBLE) | |
1384 | IEEE 64-bit (double precision) floating point format. | |
1385 | ||
1386 | @item 3 (NF_COMPLEX) | |
1387 | @item 4 (NF_COMPLEX16) | |
1388 | @item 5 (NF_COMPLEX32) | |
3d4cf720 JK |
1389 | @c "GDB source" really means @file{include/aout/stab_gnu.h}, but trying |
1390 | @c to put that here got an overfull hbox. | |
1391 | These are for complex numbers. A comment in the GDB source describes | |
685a5e86 DM |
1392 | them as Fortran @code{complex}, @code{double complex}, and |
1393 | @code{complex*16}, respectively, but what does that mean? (i.e., Single | |
1394 | precision? Double precison?). | |
1a8b5668 JK |
1395 | |
1396 | @item 6 (NF_LDOUBLE) | |
43603088 | 1397 | Long double. This should probably only be used for Sun format |
685a5e86 DM |
1398 | @code{long double}, and new codes should be used for other floating |
1399 | point formats (@code{NF_DOUBLE} can be used if a @code{long double} is | |
1400 | really just an IEEE double, of course). | |
1a8b5668 JK |
1401 | @end table |
1402 | ||
1403 | @var{bytes} is the number of bytes occupied by the type. This allows a | |
1404 | debugger to perform some operations with the type even if it doesn't | |
685a5e86 | 1405 | understand @var{fp-type}. |
8c59ee11 JK |
1406 | |
1407 | @item g @var{type-information} ; @var{nbits} | |
1408 | Documented by AIX to define a floating type, but their compiler actually | |
bf9d2537 | 1409 | uses negative type numbers (@pxref{Negative Type Numbers}). |
8c59ee11 JK |
1410 | |
1411 | @item c @var{type-information} ; @var{nbits} | |
1412 | Documented by AIX to define a complex type, but their compiler actually | |
bf9d2537 | 1413 | uses negative type numbers (@pxref{Negative Type Numbers}). |
8c59ee11 JK |
1414 | @end table |
1415 | ||
1416 | The C @code{void} type is defined as a signed integral type 0 bits long: | |
1417 | @example | |
1418 | .stabs "void:t19=bs0;0;0",128,0,0,0 | |
1419 | @end example | |
e9f687d5 JK |
1420 | The Solaris compiler seems to omit the trailing semicolon in this case. |
1421 | Getting sloppy in this way is not a swift move because if a type is | |
1422 | embedded in a more complex expression it is necessary to be able to tell | |
1423 | where it ends. | |
8c59ee11 JK |
1424 | |
1425 | I'm not sure how a boolean type is represented. | |
1426 | ||
bf9d2537 DM |
1427 | @node Negative Type Numbers |
1428 | @subsection Negative Type Numbers | |
8c59ee11 | 1429 | |
685a5e86 | 1430 | This is the method used in XCOFF for defining builtin types. |
8c59ee11 JK |
1431 | Since the debugger knows about the builtin types anyway, the idea of |
1432 | negative type numbers is simply to give a special type number which | |
685a5e86 | 1433 | indicates the builtin type. There is no stab defining these types. |
8c59ee11 | 1434 | |
23afb447 JK |
1435 | There are several subtle issues with negative type numbers. |
1436 | ||
1437 | One is the size of the type. A builtin type (for example the C types | |
1438 | @code{int} or @code{long}) might have different sizes depending on | |
1439 | compiler options, the target architecture, the ABI, etc. This issue | |
1440 | doesn't come up for IBM tools since (so far) they just target the | |
1441 | RS/6000; the sizes indicated below for each size are what the IBM | |
1442 | RS/6000 tools use. To deal with differing sizes, either define separate | |
1443 | negative type numbers for each size (which works but requires changing | |
1444 | the debugger, and, unless you get both AIX dbx and GDB to accept the | |
1445 | change, introduces an incompatibility), or use a type attribute | |
1446 | (@pxref{String Field}) to define a new type with the appropriate size | |
1447 | (which merely requires a debugger which understands type attributes, | |
1448 | like AIX dbx). For example, | |
1449 | ||
1450 | @example | |
1451 | .stabs "boolean:t10=@@s8;-16",128,0,0,0 | |
1452 | @end example | |
1453 | ||
1454 | defines an 8-bit boolean type, and | |
1455 | ||
1456 | @example | |
1457 | .stabs "boolean:t10=@@s64;-16",128,0,0,0 | |
1458 | @end example | |
1459 | ||
1460 | defines a 64-bit boolean type. | |
1461 | ||
1462 | A similar issue is the format of the type. This comes up most often for | |
1463 | floating-point types, which could have various formats (particularly | |
1464 | extended doubles, which vary quite a bit even among IEEE systems). | |
1465 | Again, it is best to define a new negative type number for each | |
1466 | different format; changing the format based on the target system has | |
1467 | various problems. One such problem is that the Alpha has both VAX and | |
1468 | IEEE floating types. One can easily imagine one library using the VAX | |
1469 | types and another library in the same executable using the IEEE types. | |
1470 | Another example is that the interpretation of whether a boolean is true | |
1471 | or false can be based on the least significant bit, most significant | |
1472 | bit, whether it is zero, etc., and different compilers (or different | |
1473 | options to the same compiler) might provide different kinds of boolean. | |
1474 | ||
1475 | The last major issue is the names of the types. The name of a given | |
1476 | type depends @emph{only} on the negative type number given; these do not | |
1477 | vary depending on the language, the target system, or anything else. | |
1478 | One can always define separate type numbers---in the following list you | |
1479 | will see for example separate @code{int} and @code{integer*4} types | |
1480 | which are identical except for the name. But compatibility can be | |
1481 | maintained by not inventing new negative type numbers and instead just | |
1482 | defining a new type with a new name. For example: | |
1483 | ||
1484 | @example | |
1485 | .stabs "CARDINAL:t10=-8",128,0,0,0 | |
1486 | @end example | |
1487 | ||
1488 | Here is the list of negative type numbers. The phrase @dfn{integral | |
1489 | type} is used to mean twos-complement (I strongly suspect that all | |
1490 | machines which use stabs use twos-complement; most machines use | |
1491 | twos-complement these days). | |
b273dc0f | 1492 | |
8c59ee11 JK |
1493 | @table @code |
1494 | @item -1 | |
1495 | @code{int}, 32 bit signed integral type. | |
1496 | ||
1497 | @item -2 | |
dd8126d9 | 1498 | @code{char}, 8 bit type holding a character. Both GDB and dbx on AIX |
8c59ee11 | 1499 | treat this as signed. GCC uses this type whether @code{char} is signed |
685a5e86 | 1500 | or not, which seems like a bad idea. The AIX compiler (@code{xlc}) seems to |
8c59ee11 JK |
1501 | avoid this type; it uses -5 instead for @code{char}. |
1502 | ||
1503 | @item -3 | |
1504 | @code{short}, 16 bit signed integral type. | |
1505 | ||
1506 | @item -4 | |
1507 | @code{long}, 32 bit signed integral type. | |
1508 | ||
1509 | @item -5 | |
1510 | @code{unsigned char}, 8 bit unsigned integral type. | |
1511 | ||
1512 | @item -6 | |
1513 | @code{signed char}, 8 bit signed integral type. | |
1514 | ||
1515 | @item -7 | |
1516 | @code{unsigned short}, 16 bit unsigned integral type. | |
1517 | ||
1518 | @item -8 | |
1519 | @code{unsigned int}, 32 bit unsigned integral type. | |
1520 | ||
1521 | @item -9 | |
1522 | @code{unsigned}, 32 bit unsigned integral type. | |
1523 | ||
1524 | @item -10 | |
1525 | @code{unsigned long}, 32 bit unsigned integral type. | |
1526 | ||
1527 | @item -11 | |
1528 | @code{void}, type indicating the lack of a value. | |
1529 | ||
1530 | @item -12 | |
1531 | @code{float}, IEEE single precision. | |
1532 | ||
1533 | @item -13 | |
1534 | @code{double}, IEEE double precision. | |
1535 | ||
1536 | @item -14 | |
b273dc0f JK |
1537 | @code{long double}, IEEE double precision. The compiler claims the size |
1538 | will increase in a future release, and for binary compatibility you have | |
1539 | to avoid using @code{long double}. I hope when they increase it they | |
1540 | use a new negative type number. | |
8c59ee11 JK |
1541 | |
1542 | @item -15 | |
b273dc0f | 1543 | @code{integer}. 32 bit signed integral type. |
8c59ee11 JK |
1544 | |
1545 | @item -16 | |
455c8603 JK |
1546 | @code{boolean}. 32 bit type. How is the truth value encoded? Is it |
1547 | the least significant bit or is it a question of whether the whole value | |
1548 | is zero or non-zero? | |
8c59ee11 JK |
1549 | |
1550 | @item -17 | |
b273dc0f | 1551 | @code{short real}. IEEE single precision. |
8c59ee11 JK |
1552 | |
1553 | @item -18 | |
b273dc0f | 1554 | @code{real}. IEEE double precision. |
8c59ee11 JK |
1555 | |
1556 | @item -19 | |
b273dc0f | 1557 | @code{stringptr}. @xref{Strings}. |
8c59ee11 JK |
1558 | |
1559 | @item -20 | |
dcb9e869 | 1560 | @code{character}, 8 bit unsigned character type. |
8c59ee11 JK |
1561 | |
1562 | @item -21 | |
6fe91f2c | 1563 | @code{logical*1}, 8 bit type. This Fortran type has a split |
01c4b039 | 1564 | personality in that it is used for boolean variables, but can also be |
03ffea63 JK |
1565 | used for unsigned integers. 0 is false, 1 is true, and other values are |
1566 | non-boolean. | |
8c59ee11 JK |
1567 | |
1568 | @item -22 | |
6fe91f2c | 1569 | @code{logical*2}, 16 bit type. This Fortran type has a split |
01c4b039 | 1570 | personality in that it is used for boolean variables, but can also be |
03ffea63 JK |
1571 | used for unsigned integers. 0 is false, 1 is true, and other values are |
1572 | non-boolean. | |
8c59ee11 JK |
1573 | |
1574 | @item -23 | |
6fe91f2c | 1575 | @code{logical*4}, 32 bit type. This Fortran type has a split |
01c4b039 | 1576 | personality in that it is used for boolean variables, but can also be |
03ffea63 JK |
1577 | used for unsigned integers. 0 is false, 1 is true, and other values are |
1578 | non-boolean. | |
8c59ee11 JK |
1579 | |
1580 | @item -24 | |
6fe91f2c | 1581 | @code{logical}, 32 bit type. This Fortran type has a split |
0e84d6ec | 1582 | personality in that it is used for boolean variables, but can also be |
03ffea63 JK |
1583 | used for unsigned integers. 0 is false, 1 is true, and other values are |
1584 | non-boolean. | |
8c59ee11 JK |
1585 | |
1586 | @item -25 | |
b273dc0f JK |
1587 | @code{complex}. A complex type consisting of two IEEE single-precision |
1588 | floating point values. | |
8c59ee11 JK |
1589 | |
1590 | @item -26 | |
b273dc0f JK |
1591 | @code{complex}. A complex type consisting of two IEEE double-precision |
1592 | floating point values. | |
8c59ee11 JK |
1593 | |
1594 | @item -27 | |
1595 | @code{integer*1}, 8 bit signed integral type. | |
1596 | ||
1597 | @item -28 | |
1598 | @code{integer*2}, 16 bit signed integral type. | |
1599 | ||
1600 | @item -29 | |
1601 | @code{integer*4}, 32 bit signed integral type. | |
1602 | ||
1603 | @item -30 | |
dcb9e869 JK |
1604 | @code{wchar}. Wide character, 16 bits wide, unsigned (what format? |
1605 | Unicode?). | |
8c59ee11 JK |
1606 | @end table |
1607 | ||
bf9d2537 DM |
1608 | @node Miscellaneous Types |
1609 | @section Miscellaneous Types | |
8c59ee11 JK |
1610 | |
1611 | @table @code | |
1612 | @item b @var{type-information} ; @var{bytes} | |
1613 | Pascal space type. This is documented by IBM; what does it mean? | |
1614 | ||
685a5e86 | 1615 | This use of the @samp{b} type descriptor can be distinguished |
bf9d2537 DM |
1616 | from its use for builtin integral types (@pxref{Builtin Type |
1617 | Descriptors}) because the character following the type descriptor is | |
8c59ee11 JK |
1618 | always a digit, @samp{(}, or @samp{-}. |
1619 | ||
1620 | @item B @var{type-information} | |
43603088 | 1621 | A volatile-qualified version of @var{type-information}. This is |
685a5e86 | 1622 | a Sun extension. References and stores to a variable with a |
43603088 | 1623 | volatile-qualified type must not be optimized or cached; they |
685a5e86 | 1624 | must occur as the user specifies them. |
8c59ee11 JK |
1625 | |
1626 | @item d @var{type-information} | |
1627 | File of type @var{type-information}. As far as I know this is only used | |
1628 | by Pascal. | |
1629 | ||
1630 | @item k @var{type-information} | |
43603088 JK |
1631 | A const-qualified version of @var{type-information}. This is a Sun |
1632 | extension. A variable with a const-qualified type cannot be modified. | |
8c59ee11 JK |
1633 | |
1634 | @item M @var{type-information} ; @var{length} | |
1635 | Multiple instance type. The type seems to composed of @var{length} | |
1636 | repetitions of @var{type-information}, for example @code{character*3} is | |
1637 | represented by @samp{M-2;3}, where @samp{-2} is a reference to a | |
bf9d2537 | 1638 | character type (@pxref{Negative Type Numbers}). I'm not sure how this |
6fe91f2c DM |
1639 | differs from an array. This appears to be a Fortran feature. |
1640 | @var{length} is a bound, like those in range types; see @ref{Subranges}. | |
8c59ee11 JK |
1641 | |
1642 | @item S @var{type-information} | |
1643 | Pascal set type. @var{type-information} must be a small type such as an | |
1644 | enumeration or a subrange, and the type is a bitmask whose length is | |
1645 | specified by the number of elements in @var{type-information}. | |
1646 | ||
168e8087 JK |
1647 | In CHILL, if it is a bitstring instead of a set, also use the @samp{S} |
1648 | type attribute (@pxref{String Field}). | |
1649 | ||
8c59ee11 JK |
1650 | @item * @var{type-information} |
1651 | Pointer to @var{type-information}. | |
139741da | 1652 | @end table |
e505224d | 1653 | |
bf9d2537 DM |
1654 | @node Cross-References |
1655 | @section Cross-References to Other Types | |
8c59ee11 | 1656 | |
685a5e86 DM |
1657 | A type can be used before it is defined; one common way to deal with |
1658 | that situation is just to use a type reference to a type which has not | |
1659 | yet been defined. | |
8c59ee11 JK |
1660 | |
1661 | Another way is with the @samp{x} type descriptor, which is followed by | |
1662 | @samp{s} for a structure tag, @samp{u} for a union tag, or @samp{e} for | |
1663 | a enumerator tag, followed by the name of the tag, followed by @samp{:}. | |
6c06a518 JK |
1664 | If the name contains @samp{::} between a @samp{<} and @samp{>} pair (for |
1665 | C++ templates), such a @samp{::} does not end the name---only a single | |
1666 | @samp{:} ends the name; see @ref{Nested Symbols}. | |
f50cb1a3 | 1667 | |
685a5e86 | 1668 | For example, the following C declarations: |
e505224d PB |
1669 | |
1670 | @example | |
8c59ee11 JK |
1671 | struct foo; |
1672 | struct foo *bar; | |
e505224d PB |
1673 | @end example |
1674 | ||
685a5e86 DM |
1675 | @noindent |
1676 | produce: | |
8c59ee11 JK |
1677 | |
1678 | @example | |
1679 | .stabs "bar:G16=*17=xsfoo:",32,0,0,0 | |
1680 | @end example | |
1681 | ||
1682 | Not all debuggers support the @samp{x} type descriptor, so on some | |
1683 | machines GCC does not use it. I believe that for the above example it | |
1684 | would just emit a reference to type 17 and never define it, but I | |
1685 | haven't verified that. | |
1686 | ||
1687 | Modula-2 imported types, at least on AIX, use the @samp{i} type | |
1688 | descriptor, which is followed by the name of the module from which the | |
1689 | type is imported, followed by @samp{:}, followed by the name of the | |
1690 | type. There is then optionally a comma followed by type information for | |
685a5e86 | 1691 | the type. This differs from merely naming the type (@pxref{Typedefs}) in |
8c59ee11 JK |
1692 | that it identifies the module; I don't understand whether the name of |
1693 | the type given here is always just the same as the name we are giving | |
1694 | it, or whether this type descriptor is used with a nameless stab | |
bf9d2537 | 1695 | (@pxref{String Field}), or what. The symbol ends with @samp{;}. |
e505224d | 1696 | |
8c59ee11 | 1697 | @node Subranges |
bf9d2537 | 1698 | @section Subrange Types |
8c59ee11 JK |
1699 | |
1700 | The @samp{r} type descriptor defines a type as a subrange of another | |
685a5e86 DM |
1701 | type. It is followed by type information for the type of which it is a |
1702 | subrange, a semicolon, an integral lower bound, a semicolon, an | |
8c59ee11 | 1703 | integral upper bound, and a semicolon. The AIX documentation does not |
63cef7d7 JK |
1704 | specify the trailing semicolon, in an effort to specify array indexes |
1705 | more cleanly, but a subrange which is not an array index has always | |
466bdeb2 | 1706 | included a trailing semicolon (@pxref{Arrays}). |
8c59ee11 | 1707 | |
8cfe3beb | 1708 | Instead of an integer, either bound can be one of the following: |
8c59ee11 JK |
1709 | |
1710 | @table @code | |
1711 | @item A @var{offset} | |
1712 | The bound is passed by reference on the stack at offset @var{offset} | |
1713 | from the argument list. @xref{Parameters}, for more information on such | |
1714 | offsets. | |
1715 | ||
1716 | @item T @var{offset} | |
1717 | The bound is passed by value on the stack at offset @var{offset} from | |
1718 | the argument list. | |
1719 | ||
1720 | @item a @var{register-number} | |
1721 | The bound is pased by reference in register number | |
1722 | @var{register-number}. | |
1723 | ||
1724 | @item t @var{register-number} | |
1725 | The bound is passed by value in register number @var{register-number}. | |
1726 | ||
1727 | @item J | |
1728 | There is no bound. | |
1729 | @end table | |
1730 | ||
bf9d2537 | 1731 | Subranges are also used for builtin types; see @ref{Traditional Builtin Types}. |
8c59ee11 JK |
1732 | |
1733 | @node Arrays | |
bf9d2537 | 1734 | @section Array Types |
8c59ee11 JK |
1735 | |
1736 | Arrays use the @samp{a} type descriptor. Following the type descriptor | |
63cef7d7 | 1737 | is the type of the index and the type of the array elements. If the |
685a5e86 DM |
1738 | index type is a range type, it ends in a semicolon; otherwise |
1739 | (for example, if it is a type reference), there does not | |
63cef7d7 JK |
1740 | appear to be any way to tell where the types are separated. In an |
1741 | effort to clean up this mess, IBM documents the two types as being | |
1742 | separated by a semicolon, and a range type as not ending in a semicolon | |
1743 | (but this is not right for range types which are not array indexes, | |
1744 | @pxref{Subranges}). I think probably the best solution is to specify | |
1745 | that a semicolon ends a range type, and that the index type and element | |
1746 | type of an array are separated by a semicolon, but that if the index | |
1747 | type is a range type, the extra semicolon can be omitted. GDB (at least | |
1748 | through version 4.9) doesn't support any kind of index type other than a | |
1749 | range anyway; I'm not sure about dbx. | |
6aa83a79 | 1750 | |
ee59134e | 1751 | It is well established, and widely used, that the type of the index, |
3d4cf720 | 1752 | unlike most types found in the stabs, is merely a type definition, not |
bf9d2537 | 1753 | type information (@pxref{String Field}) (that is, it need not start with |
685a5e86 | 1754 | @samp{@var{type-number}=} if it is defining a new type). According to a |
3d4cf720 JK |
1755 | comment in GDB, this is also true of the type of the array elements; it |
1756 | gives @samp{ar1;1;10;ar1;1;10;4} as a legitimate way to express a two | |
1757 | dimensional array. According to AIX documentation, the element type | |
1758 | must be type information. GDB accepts either. | |
ee59134e | 1759 | |
43603088 JK |
1760 | The type of the index is often a range type, expressed as the type |
1761 | descriptor @samp{r} and some parameters. It defines the size of the | |
1762 | array. In the example below, the range @samp{r1;0;2;} defines an index | |
1763 | type which is a subrange of type 1 (integer), with a lower bound of 0 | |
1764 | and an upper bound of 2. This defines the valid range of subscripts of | |
1765 | a three-element C array. | |
e505224d | 1766 | |
685a5e86 | 1767 | For example, the definition: |
e505224d PB |
1768 | |
1769 | @example | |
8c59ee11 JK |
1770 | char char_vec[3] = @{'a','b','c'@}; |
1771 | @end example | |
e505224d | 1772 | |
8c59ee11 | 1773 | @noindent |
685a5e86 | 1774 | produces the output: |
8c59ee11 JK |
1775 | |
1776 | @example | |
1777 | .stabs "char_vec:G19=ar1;0;2;2",32,0,0,0 | |
1778 | .global _char_vec | |
1779 | .align 4 | |
1780 | _char_vec: | |
1781 | .byte 97 | |
1782 | .byte 98 | |
1783 | .byte 99 | |
1784 | @end example | |
1785 | ||
685a5e86 | 1786 | If an array is @dfn{packed}, the elements are spaced more |
8c59ee11 JK |
1787 | closely than normal, saving memory at the expense of speed. For |
1788 | example, an array of 3-byte objects might, if unpacked, have each | |
1789 | element aligned on a 4-byte boundary, but if packed, have no padding. | |
1790 | One way to specify that something is packed is with type attributes | |
bf9d2537 | 1791 | (@pxref{String Field}). In the case of arrays, another is to use the |
8c59ee11 JK |
1792 | @samp{P} type descriptor instead of @samp{a}. Other than specifying a |
1793 | packed array, @samp{P} is identical to @samp{a}. | |
1794 | ||
1795 | @c FIXME-what is it? A pointer? | |
1796 | An open array is represented by the @samp{A} type descriptor followed by | |
1797 | type information specifying the type of the array elements. | |
1798 | ||
1799 | @c FIXME: what is the format of this type? A pointer to a vector of pointers? | |
1800 | An N-dimensional dynamic array is represented by | |
1801 | ||
1802 | @example | |
1803 | D @var{dimensions} ; @var{type-information} | |
1804 | @end example | |
1805 | ||
1806 | @c Does dimensions really have this meaning? The AIX documentation | |
1807 | @c doesn't say. | |
1808 | @var{dimensions} is the number of dimensions; @var{type-information} | |
1809 | specifies the type of the array elements. | |
1810 | ||
1811 | @c FIXME: what is the format of this type? A pointer to some offsets in | |
1812 | @c another array? | |
1813 | A subarray of an N-dimensional array is represented by | |
1814 | ||
1815 | @example | |
1816 | E @var{dimensions} ; @var{type-information} | |
e505224d PB |
1817 | @end example |
1818 | ||
8c59ee11 JK |
1819 | @c Does dimensions really have this meaning? The AIX documentation |
1820 | @c doesn't say. | |
1821 | @var{dimensions} is the number of dimensions; @var{type-information} | |
1822 | specifies the type of the array elements. | |
1823 | ||
1824 | @node Strings | |
1825 | @section Strings | |
1826 | ||
1827 | Some languages, like C or the original Pascal, do not have string types, | |
1828 | they just have related things like arrays of characters. But most | |
1829 | Pascals and various other languages have string types, which are | |
1830 | indicated as follows: | |
1831 | ||
1832 | @table @code | |
1833 | @item n @var{type-information} ; @var{bytes} | |
1834 | @var{bytes} is the maximum length. I'm not sure what | |
1835 | @var{type-information} is; I suspect that it means that this is a string | |
1836 | of @var{type-information} (thus allowing a string of integers, a string | |
1837 | of wide characters, etc., as well as a string of characters). Not sure | |
1838 | what the format of this type is. This is an AIX feature. | |
1839 | ||
1840 | @item z @var{type-information} ; @var{bytes} | |
1841 | Just like @samp{n} except that this is a gstring, not an ordinary | |
1842 | string. I don't know the difference. | |
1843 | ||
1844 | @item N | |
1845 | Pascal Stringptr. What is this? This is an AIX feature. | |
1846 | @end table | |
1847 | ||
168e8087 JK |
1848 | Languages, such as CHILL which have a string type which is basically |
1849 | just an array of characters use the @samp{S} type attribute | |
1850 | (@pxref{String Field}). | |
1851 | ||
899bafeb | 1852 | @node Enumerations |
6fe91f2c | 1853 | @section Enumerations |
e505224d | 1854 | |
8c59ee11 | 1855 | Enumerations are defined with the @samp{e} type descriptor. |
e505224d | 1856 | |
8c59ee11 JK |
1857 | @c FIXME: Where does this information properly go? Perhaps it is |
1858 | @c redundant with something we already explain. | |
685a5e86 | 1859 | The source line below declares an enumeration type at file scope. |
6fe91f2c DM |
1860 | The type definition is located after the @code{N_RBRAC} that marks the end of |
1861 | the previous procedure's block scope, and before the @code{N_FUN} that marks | |
8c59ee11 | 1862 | the beginning of the next procedure's block scope. Therefore it does not |
6fe91f2c | 1863 | describe a block local symbol, but a file local one. |
8c59ee11 JK |
1864 | |
1865 | The source line: | |
e505224d PB |
1866 | |
1867 | @example | |
8c59ee11 | 1868 | enum e_places @{first,second=3,last@}; |
e505224d PB |
1869 | @end example |
1870 | ||
899bafeb | 1871 | @noindent |
685a5e86 | 1872 | generates the following stab: |
e505224d | 1873 | |
899bafeb | 1874 | @example |
8c59ee11 | 1875 | .stabs "e_places:T22=efirst:0,second:3,last:4,;",128,0,0,0 |
899bafeb | 1876 | @end example |
e505224d | 1877 | |
685a5e86 DM |
1878 | The symbol descriptor (@samp{T}) says that the stab describes a |
1879 | structure, enumeration, or union tag. The type descriptor @samp{e}, | |
1880 | following the @samp{22=} of the type definition narrows it down to an | |
1881 | enumeration type. Following the @samp{e} is a list of the elements of | |
1882 | the enumeration. The format is @samp{@var{name}:@var{value},}. The | |
ae701604 JK |
1883 | list of elements ends with @samp{;}. The fact that @var{value} is |
1884 | specified as an integer can cause problems if the value is large. GCC | |
1885 | 2.5.2 tries to output it in octal in that case with a leading zero, | |
1886 | which is probably a good thing, although GDB 4.11 supports octal only in | |
1887 | cases where decimal is perfectly good. Negative decimal values are | |
1888 | supported by both GDB and dbx. | |
e505224d | 1889 | |
8c59ee11 JK |
1890 | There is no standard way to specify the size of an enumeration type; it |
1891 | is determined by the architecture (normally all enumerations types are | |
ae701604 JK |
1892 | 32 bits). Type attributes can be used to specify an enumeration type of |
1893 | another size for debuggers which support them; see @ref{String Field}. | |
8c59ee11 JK |
1894 | |
1895 | @node Structures | |
1896 | @section Structures | |
e505224d | 1897 | |
685a5e86 | 1898 | The encoding of structures in stabs can be shown with an example. |
e505224d PB |
1899 | |
1900 | The following source code declares a structure tag and defines an | |
685a5e86 DM |
1901 | instance of the structure in global scope. Then a @code{typedef} equates the |
1902 | structure tag with a new type. Seperate stabs are generated for the | |
1903 | structure tag, the structure @code{typedef}, and the structure instance. The | |
1904 | stabs for the tag and the @code{typedef} are emited when the definitions are | |
e505224d PB |
1905 | encountered. Since the structure elements are not initialized, the |
1906 | stab and code for the structure variable itself is located at the end | |
685a5e86 | 1907 | of the program in the bss section. |
e505224d PB |
1908 | |
1909 | @example | |
685a5e86 DM |
1910 | struct s_tag @{ |
1911 | int s_int; | |
1912 | float s_float; | |
1913 | char s_char_vec[8]; | |
1914 | struct s_tag* s_next; | |
1915 | @} g_an_s; | |
e505224d | 1916 | |
685a5e86 DM |
1917 | typedef struct s_tag s_typedef; |
1918 | @end example | |
e505224d | 1919 | |
685a5e86 DM |
1920 | The structure tag has an @code{N_LSYM} stab type because, like the |
1921 | enumeration, the symbol has file scope. Like the enumeration, the | |
1922 | symbol descriptor is @samp{T}, for enumeration, structure, or tag type. | |
43603088 | 1923 | The type descriptor @samp{s} following the @samp{16=} of the type |
685a5e86 | 1924 | definition narrows the symbol type to structure. |
e505224d | 1925 | |
43603088 | 1926 | Following the @samp{s} type descriptor is the number of bytes the |
685a5e86 DM |
1927 | structure occupies, followed by a description of each structure element. |
1928 | The structure element descriptions are of the form @var{name:type, bit | |
1929 | offset from the start of the struct, number of bits in the element}. | |
e505224d | 1930 | |
43603088 JK |
1931 | @c FIXME: phony line break. Can probably be fixed by using an example |
1932 | @c with fewer fields. | |
685a5e86 | 1933 | @example |
43603088 | 1934 | # @r{128 is N_LSYM} |
685a5e86 DM |
1935 | .stabs "s_tag:T16=s20s_int:1,0,32;s_float:12,32,32; |
1936 | s_char_vec:17=ar1;0;7;2,64,64;s_next:18=*16,128,32;;",128,0,0,0 | |
612dbd4c | 1937 | @end example |
6fe91f2c | 1938 | |
685a5e86 DM |
1939 | In this example, the first two structure elements are previously defined |
1940 | types. For these, the type following the @samp{@var{name}:} part of the | |
1941 | element description is a simple type reference. The other two structure | |
e505224d | 1942 | elements are new types. In this case there is a type definition |
685a5e86 DM |
1943 | embedded after the @samp{@var{name}:}. The type definition for the |
1944 | array element looks just like a type definition for a standalone array. | |
1945 | The @code{s_next} field is a pointer to the same kind of structure that | |
1946 | the field is an element of. So the definition of structure type 16 | |
1947 | contains a type definition for an element which is a pointer to type 16. | |
e505224d | 1948 | |
6c06a518 JK |
1949 | If a field is a static member (this is a C++ feature in which a single |
1950 | variable appears to be a field of every structure of a given type) it | |
1951 | still starts out with the field name, a colon, and the type, but then | |
1952 | instead of a comma, bit position, comma, and bit size, there is a colon | |
1953 | followed by the name of the variable which each such field refers to. | |
1954 | ||
1955 | If the structure has methods (a C++ feature), they follow the non-method | |
1956 | fields; see @ref{Cplusplus}. | |
1957 | ||
899bafeb | 1958 | @node Typedefs |
bf9d2537 | 1959 | @section Giving a Type a Name |
e505224d | 1960 | |
e7bb76cc | 1961 | To give a type a name, use the @samp{t} symbol descriptor. The type |
bf9d2537 | 1962 | is specified by the type information (@pxref{String Field}) for the stab. |
e7bb76cc | 1963 | For example, |
e505224d | 1964 | |
899bafeb | 1965 | @example |
43603088 | 1966 | .stabs "s_typedef:t16",128,0,0,0 # @r{128 is N_LSYM} |
899bafeb | 1967 | @end example |
e505224d | 1968 | |
8c59ee11 | 1969 | specifies that @code{s_typedef} refers to type number 16. Such stabs |
43603088 | 1970 | have symbol type @code{N_LSYM} (or @code{C_DECL} for XCOFF). |
e505224d | 1971 | |
685a5e86 | 1972 | If you are specifying the tag name for a structure, union, or |
8c59ee11 JK |
1973 | enumeration, use the @samp{T} symbol descriptor instead. I believe C is |
1974 | the only language with this feature. | |
e505224d | 1975 | |
8c59ee11 JK |
1976 | If the type is an opaque type (I believe this is a Modula-2 feature), |
1977 | AIX provides a type descriptor to specify it. The type descriptor is | |
1978 | @samp{o} and is followed by a name. I don't know what the name | |
1979 | means---is it always the same as the name of the type, or is this type | |
bf9d2537 | 1980 | descriptor used with a nameless stab (@pxref{String Field})? There |
8c59ee11 JK |
1981 | optionally follows a comma followed by type information which defines |
1982 | the type of this type. If omitted, a semicolon is used in place of the | |
e7bb76cc | 1983 | comma and the type information, and the type is much like a generic |
8c59ee11 JK |
1984 | pointer type---it has a known size but little else about it is |
1985 | specified. | |
e505224d | 1986 | |
899bafeb | 1987 | @node Unions |
6fe91f2c | 1988 | @section Unions |
e505224d | 1989 | |
e505224d | 1990 | @example |
685a5e86 DM |
1991 | union u_tag @{ |
1992 | int u_int; | |
1993 | float u_float; | |
1994 | char* u_char; | |
1995 | @} an_u; | |
e505224d PB |
1996 | @end example |
1997 | ||
685a5e86 DM |
1998 | This code generates a stab for a union tag and a stab for a union |
1999 | variable. Both use the @code{N_LSYM} stab type. If a union variable is | |
e505224d | 2000 | scoped locally to the procedure in which it is defined, its stab is |
6fe91f2c | 2001 | located immediately preceding the @code{N_LBRAC} for the procedure's block |
e505224d PB |
2002 | start. |
2003 | ||
685a5e86 | 2004 | The stab for the union tag, however, is located preceding the code for |
6fe91f2c | 2005 | the procedure in which it is defined. The stab type is @code{N_LSYM}. This |
e505224d | 2006 | would seem to imply that the union type is file scope, like the struct |
f958d5cd DM |
2007 | type @code{s_tag}. This is not true. The contents and position of the stab |
2008 | for @code{u_type} do not convey any infomation about its procedure local | |
e505224d PB |
2009 | scope. |
2010 | ||
43603088 JK |
2011 | @c FIXME: phony line break. Can probably be fixed by using an example |
2012 | @c with fewer fields. | |
5bc927fb | 2013 | @smallexample |
43603088 | 2014 | # @r{128 is N_LSYM} |
685a5e86 DM |
2015 | .stabs "u_tag:T23=u4u_int:1,0,32;u_float:12,0,32;u_char:21,0,32;;", |
2016 | 128,0,0,0 | |
5bc927fb | 2017 | @end smallexample |
e505224d | 2018 | |
685a5e86 DM |
2019 | The symbol descriptor @samp{T}, following the @samp{name:} means that |
2020 | the stab describes an enumeration, structure, or union tag. The type | |
2021 | descriptor @samp{u}, following the @samp{23=} of the type definition, | |
2022 | narrows it down to a union type definition. Following the @samp{u} is | |
2023 | the number of bytes in the union. After that is a list of union element | |
2024 | descriptions. Their format is @var{name:type, bit offset into the | |
2025 | union, number of bytes for the element;}. | |
e505224d | 2026 | |
685a5e86 | 2027 | The stab for the union variable is: |
e505224d | 2028 | |
899bafeb | 2029 | @example |
43603088 | 2030 | .stabs "an_u:23",128,0,0,-20 # @r{128 is N_LSYM} |
899bafeb | 2031 | @end example |
e505224d | 2032 | |
43603088 | 2033 | @samp{-20} specifies where the variable is stored (@pxref{Stack |
bf9d2537 | 2034 | Variables}). |
43603088 | 2035 | |
bf9d2537 DM |
2036 | @node Function Types |
2037 | @section Function Types | |
e505224d | 2038 | |
685a5e86 DM |
2039 | Various types can be defined for function variables. These types are |
2040 | not used in defining functions (@pxref{Procedures}); they are used for | |
2041 | things like pointers to functions. | |
e505224d | 2042 | |
8c59ee11 JK |
2043 | The simple, traditional, type is type descriptor @samp{f} is followed by |
2044 | type information for the return type of the function, followed by a | |
2045 | semicolon. | |
2046 | ||
685a5e86 DM |
2047 | This does not deal with functions for which the number and types of the |
2048 | parameters are part of the type, as in Modula-2 or ANSI C. AIX provides | |
2049 | extensions to specify these, using the @samp{f}, @samp{F}, @samp{p}, and | |
2050 | @samp{R} type descriptors. | |
8c59ee11 | 2051 | |
685a5e86 | 2052 | First comes the type descriptor. If it is @samp{f} or @samp{F}, this |
43603088 JK |
2053 | type involves a function rather than a procedure, and the type |
2054 | information for the return type of the function follows, followed by a | |
2055 | comma. Then comes the number of parameters to the function and a | |
2056 | semicolon. Then, for each parameter, there is the name of the parameter | |
2057 | followed by a colon (this is only present for type descriptors @samp{R} | |
2058 | and @samp{F} which represent Pascal function or procedure parameters), | |
2059 | type information for the parameter, a comma, 0 if passed by reference or | |
2060 | 1 if passed by value, and a semicolon. The type definition ends with a | |
2061 | semicolon. | |
8c59ee11 | 2062 | |
685a5e86 | 2063 | For example, this variable definition: |
e505224d PB |
2064 | |
2065 | @example | |
8c59ee11 | 2066 | int (*g_pf)(); |
e505224d PB |
2067 | @end example |
2068 | ||
8c59ee11 JK |
2069 | @noindent |
2070 | generates the following code: | |
e505224d | 2071 | |
899bafeb | 2072 | @example |
8c59ee11 JK |
2073 | .stabs "g_pf:G24=*25=f1",32,0,0,0 |
2074 | .common _g_pf,4,"bss" | |
899bafeb | 2075 | @end example |
e505224d | 2076 | |
8c59ee11 | 2077 | The variable defines a new type, 24, which is a pointer to another new |
685a5e86 | 2078 | type, 25, which is a function returning @code{int}. |
e505224d | 2079 | |
bf9d2537 DM |
2080 | @node Symbol Tables |
2081 | @chapter Symbol Information in Symbol Tables | |
e505224d | 2082 | |
6fe91f2c DM |
2083 | This chapter describes the format of symbol table entries |
2084 | and how stab assembler directives map to them. It also describes the | |
2085 | transformations that the assembler and linker make on data from stabs. | |
e505224d | 2086 | |
685a5e86 | 2087 | @menu |
bf9d2537 DM |
2088 | * Symbol Table Format:: |
2089 | * Transformations On Symbol Tables:: | |
685a5e86 DM |
2090 | @end menu |
2091 | ||
bf9d2537 DM |
2092 | @node Symbol Table Format |
2093 | @section Symbol Table Format | |
685a5e86 DM |
2094 | |
2095 | Each time the assembler encounters a stab directive, it puts | |
2096 | each field of the stab into a corresponding field in a symbol table | |
0a95c18c | 2097 | entry of its output file. If the stab contains a string field, the |
e505224d PB |
2098 | symbol table entry for that stab points to a string table entry |
2099 | containing the string data from the stab. Assembler labels become | |
2100 | relocatable addresses. Symbol table entries in a.out have the format: | |
2101 | ||
dd8126d9 | 2102 | @c FIXME: should refer to external, not internal. |
e505224d PB |
2103 | @example |
2104 | struct internal_nlist @{ | |
139741da RP |
2105 | unsigned long n_strx; /* index into string table of name */ |
2106 | unsigned char n_type; /* type of symbol */ | |
2107 | unsigned char n_other; /* misc info (usually empty) */ | |
2108 | unsigned short n_desc; /* description field */ | |
2109 | bfd_vma n_value; /* value of symbol */ | |
e505224d PB |
2110 | @}; |
2111 | @end example | |
2112 | ||
0a95c18c JK |
2113 | If the stab has a string, the @code{n_strx} field holds the offset in |
2114 | bytes of the string within the string table. The string is terminated | |
2115 | by a NUL character. If the stab lacks a string (for example, it was | |
2116 | produced by a @code{.stabn} or @code{.stabd} directive), the | |
2117 | @code{n_strx} field is zero. | |
685a5e86 DM |
2118 | |
2119 | Symbol table entries with @code{n_type} field values greater than 0x1f | |
2120 | originated as stabs generated by the compiler (with one random | |
2121 | exception). The other entries were placed in the symbol table of the | |
2122 | executable by the assembler or the linker. | |
e505224d | 2123 | |
bf9d2537 DM |
2124 | @node Transformations On Symbol Tables |
2125 | @section Transformations on Symbol Tables | |
e505224d PB |
2126 | |
2127 | The linker concatenates object files and does fixups of externally | |
685a5e86 | 2128 | defined symbols. |
e505224d | 2129 | |
685a5e86 DM |
2130 | You can see the transformations made on stab data by the assembler and |
2131 | linker by examining the symbol table after each pass of the build. To | |
2132 | do this, use @samp{nm -ap}, which dumps the symbol table, including | |
6fe91f2c DM |
2133 | debugging information, unsorted. For stab entries the columns are: |
2134 | @var{value}, @var{other}, @var{desc}, @var{type}, @var{string}. For | |
2135 | assembler and linker symbols, the columns are: @var{value}, @var{type}, | |
2136 | @var{string}. | |
e505224d | 2137 | |
43603088 JK |
2138 | The low 5 bits of the stab type tell the linker how to relocate the |
2139 | value of the stab. Thus for stab types like @code{N_RSYM} and | |
2140 | @code{N_LSYM}, where the value is an offset or a register number, the | |
2141 | low 5 bits are @code{N_ABS}, which tells the linker not to relocate the | |
2142 | value. | |
e505224d | 2143 | |
0a95c18c | 2144 | Where the value of a stab contains an assembly language label, |
e505224d PB |
2145 | it is transformed by each build step. The assembler turns it into a |
2146 | relocatable address and the linker turns it into an absolute address. | |
685a5e86 DM |
2147 | |
2148 | @menu | |
bf9d2537 DM |
2149 | * Transformations On Static Variables:: |
2150 | * Transformations On Global Variables:: | |
b563c370 | 2151 | * ELF and SOM Transformations:: In ELF, things are a bit different. |
685a5e86 DM |
2152 | @end menu |
2153 | ||
bf9d2537 DM |
2154 | @node Transformations On Static Variables |
2155 | @subsection Transformations on Static Variables | |
685a5e86 | 2156 | |
e505224d PB |
2157 | This source line defines a static variable at file scope: |
2158 | ||
899bafeb | 2159 | @example |
685a5e86 | 2160 | static int s_g_repeat |
899bafeb | 2161 | @end example |
e505224d | 2162 | |
899bafeb | 2163 | @noindent |
6fe91f2c | 2164 | The following stab describes the symbol: |
e505224d | 2165 | |
899bafeb | 2166 | @example |
685a5e86 | 2167 | .stabs "s_g_repeat:S1",38,0,0,_s_g_repeat |
899bafeb | 2168 | @end example |
e505224d | 2169 | |
899bafeb | 2170 | @noindent |
e505224d | 2171 | The assembler transforms the stab into this symbol table entry in the |
899bafeb | 2172 | @file{.o} file. The location is expressed as a data segment offset. |
e505224d | 2173 | |
899bafeb | 2174 | @example |
685a5e86 | 2175 | 00000084 - 00 0000 STSYM s_g_repeat:S1 |
899bafeb | 2176 | @end example |
e505224d | 2177 | |
899bafeb | 2178 | @noindent |
685a5e86 | 2179 | In the symbol table entry from the executable, the linker has made the |
e505224d PB |
2180 | relocatable address absolute. |
2181 | ||
899bafeb | 2182 | @example |
685a5e86 | 2183 | 0000e00c - 00 0000 STSYM s_g_repeat:S1 |
899bafeb | 2184 | @end example |
e505224d | 2185 | |
bf9d2537 DM |
2186 | @node Transformations On Global Variables |
2187 | @subsection Transformations on Global Variables | |
685a5e86 | 2188 | |
e505224d | 2189 | Stabs for global variables do not contain location information. In |
685a5e86 | 2190 | this case, the debugger finds location information in the assembler or |
e505224d PB |
2191 | linker symbol table entry describing the variable. The source line: |
2192 | ||
899bafeb | 2193 | @example |
685a5e86 | 2194 | char g_foo = 'c'; |
899bafeb | 2195 | @end example |
e505224d | 2196 | |
899bafeb | 2197 | @noindent |
e505224d PB |
2198 | generates the stab: |
2199 | ||
899bafeb | 2200 | @example |
685a5e86 | 2201 | .stabs "g_foo:G2",32,0,0,0 |
899bafeb | 2202 | @end example |
e505224d | 2203 | |
685a5e86 DM |
2204 | The variable is represented by two symbol table entries in the object |
2205 | file (see below). The first one originated as a stab. The second one | |
2206 | is an external symbol. The upper case @samp{D} signifies that the | |
2207 | @code{n_type} field of the symbol table contains 7, @code{N_DATA} with | |
ac31351a JK |
2208 | local linkage. The stab's value is zero since the value is not used for |
2209 | @code{N_GSYM} stabs. The value of the linker symbol is the relocatable | |
2210 | address corresponding to the variable. | |
e505224d | 2211 | |
899bafeb | 2212 | @example |
685a5e86 DM |
2213 | 00000000 - 00 0000 GSYM g_foo:G2 |
2214 | 00000080 D _g_foo | |
899bafeb | 2215 | @end example |
e505224d | 2216 | |
899bafeb | 2217 | @noindent |
e505224d | 2218 | These entries as transformed by the linker. The linker symbol table |
685a5e86 | 2219 | entry now holds an absolute address: |
e505224d | 2220 | |
899bafeb | 2221 | @example |
685a5e86 | 2222 | 00000000 - 00 0000 GSYM g_foo:G2 |
899bafeb | 2223 | @dots{} |
685a5e86 | 2224 | 0000e008 D _g_foo |
899bafeb | 2225 | @end example |
e505224d | 2226 | |
e89d48dd JL |
2227 | @node ELF and SOM Transformations |
2228 | @subsection Transformations of Stabs in ELF and SOM Files | |
cd61aa60 | 2229 | |
e89d48dd | 2230 | For ELF and SOM files, use @code{objdump --stabs} instead of @code{nm} to show |
cd61aa60 JK |
2231 | the stabs in an object or executable file. @code{objdump} is a GNU |
2232 | utility; Sun does not provide any equivalent. | |
2233 | ||
2234 | The following example is for a stab whose value is an address is | |
2235 | relative to the compilation unit (@pxref{Stabs In ELF}). For example, | |
2236 | if the source line | |
2237 | ||
2238 | @example | |
2239 | static int ld = 5; | |
2240 | @end example | |
2241 | ||
2242 | appears within a function, then the assembly language output from the | |
2243 | compiler contains: | |
2244 | ||
2245 | @example | |
2246 | .Ddata.data: | |
2247 | @dots{} | |
2248 | .stabs "ld:V(0,3)",0x26,0,4,.L18-Ddata.data # @r{0x26 is N_STSYM} | |
2249 | @dots{} | |
2250 | .L18: | |
2251 | .align 4 | |
2252 | .word 0x5 | |
2253 | @end example | |
2254 | ||
2255 | Because the value is formed by subtracting one symbol from another, the | |
2256 | value is absolute, not relocatable, and so the object file contains | |
2257 | ||
2258 | @example | |
2259 | Symnum n_type n_othr n_desc n_value n_strx String | |
2260 | 31 STSYM 0 4 00000004 680 ld:V(0,3) | |
2261 | @end example | |
2262 | ||
2263 | without any relocations, and the executable file also contains | |
2264 | ||
2265 | @example | |
2266 | Symnum n_type n_othr n_desc n_value n_strx String | |
2267 | 31 STSYM 0 4 00000004 680 ld:V(0,3) | |
2268 | @end example | |
2269 | ||
8c59ee11 | 2270 | @node Cplusplus |
bf9d2537 | 2271 | @chapter GNU C++ Stabs |
e505224d PB |
2272 | |
2273 | @menu | |
bb190834 | 2274 | * Class Names:: C++ class names are both tags and typedefs. |
397f9dcd | 2275 | * Nested Symbols:: C++ symbol names can be within other types. |
bf9d2537 DM |
2276 | * Basic Cplusplus Types:: |
2277 | * Simple Classes:: | |
2278 | * Class Instance:: | |
8eb5e289 | 2279 | * Methods:: Method definition |
6fe91f2c | 2280 | * Protections:: |
bf9d2537 DM |
2281 | * Method Modifiers:: |
2282 | * Virtual Methods:: | |
6fe91f2c | 2283 | * Inheritence:: |
bf9d2537 DM |
2284 | * Virtual Base Classes:: |
2285 | * Static Members:: | |
e505224d PB |
2286 | @end menu |
2287 | ||
6fe91f2c | 2288 | Type descriptors added for C++ descriptions: |
e505224d PB |
2289 | |
2290 | @table @code | |
2291 | @item # | |
6fe91f2c | 2292 | method type (@code{##} if minimal debug) |
e505224d | 2293 | |
8c59ee11 JK |
2294 | @item @@ |
2295 | Member (class and variable) type. It is followed by type information | |
2296 | for the offset basetype, a comma, and type information for the type of | |
2297 | the field being pointed to. (FIXME: this is acknowledged to be | |
2298 | gibberish. Can anyone say what really goes here?). | |
2299 | ||
2300 | Note that there is a conflict between this and type attributes | |
bf9d2537 | 2301 | (@pxref{String Field}); both use type descriptor @samp{@@}. |
8c59ee11 JK |
2302 | Fortunately, the @samp{@@} type descriptor used in this C++ sense always |
2303 | will be followed by a digit, @samp{(}, or @samp{-}, and type attributes | |
2304 | never start with those things. | |
e505224d PB |
2305 | @end table |
2306 | ||
bb190834 JK |
2307 | @node Class Names |
2308 | @section C++ Class Names | |
2309 | ||
2310 | In C++, a class name which is declared with @code{class}, @code{struct}, | |
2311 | or @code{union}, is not only a tag, as in C, but also a type name. Thus | |
2312 | there should be stabs with both @samp{t} and @samp{T} symbol descriptors | |
2313 | (@pxref{Typedefs}). | |
2314 | ||
2315 | To save space, there is a special abbreviation for this case. If the | |
2316 | @samp{T} symbol descriptor is followed by @samp{t}, then the stab | |
2317 | defines both a type name and a tag. | |
2318 | ||
2319 | For example, the C++ code | |
2320 | ||
2321 | @example | |
2322 | struct foo @{int x;@}; | |
2323 | @end example | |
2324 | ||
2325 | can be represented as either | |
2326 | ||
2327 | @example | |
2328 | .stabs "foo:T19=s4x:1,0,32;;",128,0,0,0 # @r{128 is N_LSYM} | |
2329 | .stabs "foo:t19",128,0,0,0 | |
2330 | @end example | |
2331 | ||
2332 | or | |
2333 | ||
2334 | @example | |
2335 | .stabs "foo:Tt19=s4x:1,0,32;;",128,0,0,0 | |
2336 | @end example | |
2337 | ||
397f9dcd JK |
2338 | @node Nested Symbols |
2339 | @section Defining a Symbol Within Another Type | |
2340 | ||
2341 | In C++, a symbol (such as a type name) can be defined within another type. | |
2342 | @c FIXME: Needs example. | |
2343 | ||
2344 | In stabs, this is sometimes represented by making the name of a symbol | |
2345 | which contains @samp{::}. Such a pair of colons does not end the name | |
2346 | of the symbol, the way a single colon would (@pxref{String Field}). I'm | |
2347 | not sure how consistently used or well thought out this mechanism is. | |
2348 | So that a pair of colons in this position always has this meaning, | |
2349 | @samp{:} cannot be used as a symbol descriptor. | |
2350 | ||
2351 | For example, if the string for a stab is @samp{foo::bar::baz:t5=*6}, | |
2352 | then @code{foo::bar::baz} is the name of the symbol, @samp{t} is the | |
2353 | symbol descriptor, and @samp{5=*6} is the type information. | |
2354 | ||
bf9d2537 DM |
2355 | @node Basic Cplusplus Types |
2356 | @section Basic Types For C++ | |
e505224d PB |
2357 | |
2358 | << the examples that follow are based on a01.C >> | |
2359 | ||
2360 | ||
2361 | C++ adds two more builtin types to the set defined for C. These are | |
2362 | the unknown type and the vtable record type. The unknown type, type | |
2363 | 16, is defined in terms of itself like the void type. | |
2364 | ||
2365 | The vtable record type, type 17, is defined as a structure type and | |
6fe91f2c | 2366 | then as a structure tag. The structure has four fields: delta, index, |
e505224d PB |
2367 | pfn, and delta2. pfn is the function pointer. |
2368 | ||
2369 | << In boilerplate $vtbl_ptr_type, what are the fields delta, | |
2370 | index, and delta2 used for? >> | |
2371 | ||
2372 | This basic type is present in all C++ programs even if there are no | |
2373 | virtual methods defined. | |
2374 | ||
899bafeb | 2375 | @display |
e505224d | 2376 | .stabs "struct_name:sym_desc(type)type_def(17)=type_desc(struct)struct_bytes(8) |
139741da RP |
2377 | elem_name(delta):type_ref(short int),bit_offset(0),field_bits(16); |
2378 | elem_name(index):type_ref(short int),bit_offset(16),field_bits(16); | |
2379 | elem_name(pfn):type_def(18)=type_desc(ptr to)type_ref(void), | |
2380 | bit_offset(32),field_bits(32); | |
2381 | elem_name(delta2):type_def(short int);bit_offset(32),field_bits(16);;" | |
2382 | N_LSYM, NIL, NIL | |
899bafeb | 2383 | @end display |
6fe91f2c | 2384 | |
899bafeb | 2385 | @smallexample |
e505224d | 2386 | .stabs "$vtbl_ptr_type:t17=s8 |
139741da RP |
2387 | delta:6,0,16;index:6,16,16;pfn:18=*15,32,32;delta2:6,32,16;;" |
2388 | ,128,0,0,0 | |
899bafeb | 2389 | @end smallexample |
e505224d | 2390 | |
899bafeb | 2391 | @display |
e505224d | 2392 | .stabs "name:sym_dec(struct tag)type_ref($vtbl_ptr_type)",N_LSYM,NIL,NIL,NIL |
899bafeb | 2393 | @end display |
e505224d | 2394 | |
899bafeb | 2395 | @example |
e505224d | 2396 | .stabs "$vtbl_ptr_type:T17",128,0,0,0 |
899bafeb | 2397 | @end example |
e505224d | 2398 | |
bf9d2537 DM |
2399 | @node Simple Classes |
2400 | @section Simple Class Definition | |
e505224d PB |
2401 | |
2402 | The stabs describing C++ language features are an extension of the | |
2403 | stabs describing C. Stabs representing C++ class types elaborate | |
2404 | extensively on the stab format used to describe structure types in C. | |
2405 | Stabs representing class type variables look just like stabs | |
2406 | representing C language variables. | |
2407 | ||
2408 | Consider the following very simple class definition. | |
2409 | ||
2410 | @example | |
2411 | class baseA @{ | |
2412 | public: | |
139741da RP |
2413 | int Adat; |
2414 | int Ameth(int in, char other); | |
e505224d PB |
2415 | @}; |
2416 | @end example | |
2417 | ||
6fe91f2c | 2418 | The class @code{baseA} is represented by two stabs. The first stab describes |
e505224d | 2419 | the class as a structure type. The second stab describes a structure |
6fe91f2c | 2420 | tag of the class type. Both stabs are of stab type @code{N_LSYM}. Since the |
685a5e86 | 2421 | stab is not located between an @code{N_FUN} and an @code{N_LBRAC} stab this indicates |
6fe91f2c | 2422 | that the class is defined at file scope. If it were, then the @code{N_LSYM} |
e505224d PB |
2423 | would signify a local variable. |
2424 | ||
2425 | A stab describing a C++ class type is similar in format to a stab | |
2426 | describing a C struct, with each class member shown as a field in the | |
2427 | structure. The part of the struct format describing fields is | |
2428 | expanded to include extra information relevent to C++ class members. | |
2429 | In addition, if the class has multiple base classes or virtual | |
2430 | functions the struct format outside of the field parts is also | |
2431 | augmented. | |
2432 | ||
2433 | In this simple example the field part of the C++ class stab | |
2434 | representing member data looks just like the field part of a C struct | |
2435 | stab. The section on protections describes how its format is | |
2436 | sometimes extended for member data. | |
2437 | ||
2438 | The field part of a C++ class stab representing a member function | |
2439 | differs substantially from the field part of a C struct stab. It | |
6fe91f2c | 2440 | still begins with @samp{name:} but then goes on to define a new type number |
e505224d PB |
2441 | for the member function, describe its return type, its argument types, |
2442 | its protection level, any qualifiers applied to the method definition, | |
2443 | and whether the method is virtual or not. If the method is virtual | |
2444 | then the method description goes on to give the vtable index of the | |
2445 | method, and the type number of the first base class defining the | |
6fe91f2c | 2446 | method. |
e505224d | 2447 | |
dd8126d9 JK |
2448 | When the field name is a method name it is followed by two colons rather |
2449 | than one. This is followed by a new type definition for the method. | |
2450 | This is a number followed by an equal sign and the type descriptor | |
2451 | @samp{#}, indicating a method type, and a second @samp{#}, indicating | |
2452 | that this is the @dfn{minimal} type of method definition used by GCC2, | |
2453 | not larger method definitions used by earlier versions of GCC. This is | |
2454 | followed by a type reference showing the return type of the method and a | |
e505224d PB |
2455 | semi-colon. |
2456 | ||
dd8126d9 JK |
2457 | The format of an overloaded operator method name differs from that of |
2458 | other methods. It is @samp{op$::@var{operator-name}.} where | |
2459 | @var{operator-name} is the operator name such as @samp{+} or @samp{+=}. | |
2460 | The name ends with a period, and any characters except the period can | |
2461 | occur in the @var{operator-name} string. | |
e505224d | 2462 | |
dd8126d9 JK |
2463 | The next part of the method description represents the arguments to the |
2464 | method, preceeded by a colon and ending with a semi-colon. The types of | |
2465 | the arguments are expressed in the same way argument types are expressed | |
2466 | in C++ name mangling. In this example an @code{int} and a @code{char} | |
6fe91f2c | 2467 | map to @samp{ic}. |
e505224d PB |
2468 | |
2469 | This is followed by a number, a letter, and an asterisk or period, | |
2470 | followed by another semicolon. The number indicates the protections | |
2471 | that apply to the member function. Here the 2 means public. The | |
2472 | letter encodes any qualifier applied to the method definition. In | |
6fe91f2c | 2473 | this case, @samp{A} means that it is a normal function definition. The dot |
e505224d PB |
2474 | shows that the method is not virtual. The sections that follow |
2475 | elaborate further on these fields and describe the additional | |
2476 | information present for virtual methods. | |
2477 | ||
2478 | ||
899bafeb | 2479 | @display |
e505224d | 2480 | .stabs "class_name:sym_desc(type)type_def(20)=type_desc(struct)struct_bytes(4) |
139741da | 2481 | field_name(Adat):type(int),bit_offset(0),field_bits(32); |
e505224d | 2482 | |
139741da | 2483 | method_name(Ameth)::type_def(21)=type_desc(method)return_type(int); |
6fe91f2c | 2484 | :arg_types(int char); |
139741da RP |
2485 | protection(public)qualifier(normal)virtual(no);;" |
2486 | N_LSYM,NIL,NIL,NIL | |
899bafeb | 2487 | @end display |
e505224d | 2488 | |
899bafeb | 2489 | @smallexample |
e505224d PB |
2490 | .stabs "baseA:t20=s4Adat:1,0,32;Ameth::21=##1;:ic;2A.;;",128,0,0,0 |
2491 | ||
2492 | .stabs "class_name:sym_desc(struct tag)",N_LSYM,NIL,NIL,NIL | |
2493 | ||
2494 | .stabs "baseA:T20",128,0,0,0 | |
899bafeb | 2495 | @end smallexample |
e505224d | 2496 | |
bf9d2537 DM |
2497 | @node Class Instance |
2498 | @section Class Instance | |
e505224d PB |
2499 | |
2500 | As shown above, describing even a simple C++ class definition is | |
2501 | accomplished by massively extending the stab format used in C to | |
2502 | describe structure types. However, once the class is defined, C stabs | |
2503 | with no modifications can be used to describe class instances. The | |
2504 | following source: | |
2505 | ||
2506 | @example | |
2507 | main () @{ | |
139741da | 2508 | baseA AbaseA; |
e505224d PB |
2509 | @} |
2510 | @end example | |
2511 | ||
899bafeb RP |
2512 | @noindent |
2513 | yields the following stab describing the class instance. It looks no | |
e505224d PB |
2514 | different from a standard C stab describing a local variable. |
2515 | ||
899bafeb | 2516 | @display |
e505224d | 2517 | .stabs "name:type_ref(baseA)", N_LSYM, NIL, NIL, frame_ptr_offset |
899bafeb | 2518 | @end display |
e505224d | 2519 | |
899bafeb | 2520 | @example |
e505224d | 2521 | .stabs "AbaseA:20",128,0,0,-20 |
899bafeb | 2522 | @end example |
e505224d | 2523 | |
899bafeb | 2524 | @node Methods |
9d719a9c | 2525 | @section Method Definition |
e505224d PB |
2526 | |
2527 | The class definition shown above declares Ameth. The C++ source below | |
2528 | defines Ameth: | |
2529 | ||
2530 | @example | |
6fe91f2c DM |
2531 | int |
2532 | baseA::Ameth(int in, char other) | |
e505224d | 2533 | @{ |
139741da | 2534 | return in; |
e505224d PB |
2535 | @}; |
2536 | @end example | |
2537 | ||
2538 | ||
2539 | This method definition yields three stabs following the code of the | |
3a642a82 JK |
2540 | method. One stab describes the method itself and following two describe |
2541 | its parameters. Although there is only one formal argument all methods | |
6fe91f2c | 2542 | have an implicit argument which is the @code{this} pointer. The @code{this} |
3a642a82 JK |
2543 | pointer is a pointer to the object on which the method was called. Note |
2544 | that the method name is mangled to encode the class name and argument | |
2545 | types. Name mangling is described in the @sc{arm} (@cite{The Annotated | |
2546 | C++ Reference Manual}, by Ellis and Stroustrup, @sc{isbn} | |
2547 | 0-201-51459-1); @file{gpcompare.texi} in Cygnus GCC distributions | |
6fe91f2c | 2548 | describes the differences between GNU mangling and @sc{arm} |
3a642a82 JK |
2549 | mangling. |
2550 | @c FIXME: Use @xref, especially if this is generally installed in the | |
2551 | @c info tree. | |
2552 | @c FIXME: This information should be in a net release, either of GCC or | |
2553 | @c GDB. But gpcompare.texi doesn't seem to be in the FSF GCC. | |
e505224d | 2554 | |
612dbd4c | 2555 | @example |
e505224d | 2556 | .stabs "name:symbol_desriptor(global function)return_type(int)", |
6fe91f2c | 2557 | N_FUN, NIL, NIL, code_addr_of_method_start |
e505224d PB |
2558 | |
2559 | .stabs "Ameth__5baseAic:F1",36,0,0,_Ameth__5baseAic | |
612dbd4c | 2560 | @end example |
e505224d | 2561 | |
6fe91f2c DM |
2562 | Here is the stab for the @code{this} pointer implicit argument. The |
2563 | name of the @code{this} pointer is always @code{this}. Type 19, the | |
2564 | @code{this} pointer is defined as a pointer to type 20, @code{baseA}, | |
2565 | but a stab defining @code{baseA} has not yet been emited. Since the | |
2566 | compiler knows it will be emited shortly, here it just outputs a cross | |
2567 | reference to the undefined symbol, by prefixing the symbol name with | |
2568 | @samp{xs}. | |
e505224d | 2569 | |
612dbd4c | 2570 | @example |
e505224d | 2571 | .stabs "name:sym_desc(register param)type_def(19)= |
139741da | 2572 | type_desc(ptr to)type_ref(baseA)= |
6fe91f2c | 2573 | type_desc(cross-reference to)baseA:",N_RSYM,NIL,NIL,register_number |
e505224d | 2574 | |
c2dc518b | 2575 | .stabs "this:P19=*20=xsbaseA:",64,0,0,8 |
612dbd4c | 2576 | @end example |
e505224d PB |
2577 | |
2578 | The stab for the explicit integer argument looks just like a parameter | |
2579 | to a C function. The last field of the stab is the offset from the | |
2580 | argument pointer, which in most systems is the same as the frame | |
2581 | pointer. | |
2582 | ||
612dbd4c | 2583 | @example |
e505224d | 2584 | .stabs "name:sym_desc(value parameter)type_ref(int)", |
6fe91f2c | 2585 | N_PSYM,NIL,NIL,offset_from_arg_ptr |
e505224d PB |
2586 | |
2587 | .stabs "in:p1",160,0,0,72 | |
612dbd4c | 2588 | @end example |
e505224d PB |
2589 | |
2590 | << The examples that follow are based on A1.C >> | |
2591 | ||
899bafeb | 2592 | @node Protections |
e505224d PB |
2593 | @section Protections |
2594 | ||
e505224d PB |
2595 | In the simple class definition shown above all member data and |
2596 | functions were publicly accessable. The example that follows | |
2597 | contrasts public, protected and privately accessable fields and shows | |
2598 | how these protections are encoded in C++ stabs. | |
2599 | ||
b857d956 JK |
2600 | If the character following the @samp{@var{field-name}:} part of the |
2601 | string is @samp{/}, then the next character is the visibility. @samp{0} | |
2602 | means private, @samp{1} means protected, and @samp{2} means public. | |
2603 | Debuggers should ignore visibility characters they do not recognize, and | |
2604 | assume a reasonable default (such as public) (GDB 4.11 does not, but | |
2605 | this should be fixed in the next GDB release). If no visibility is | |
2606 | specified the field is public. The visibility @samp{9} means that the | |
2607 | field has been optimized out and is public (there is no way to specify | |
2608 | an optimized out field with a private or protected visibility). | |
2609 | Visibility @samp{9} is not supported by GDB 4.11; this should be fixed | |
2610 | in the next GDB release. | |
2611 | ||
2612 | The following C++ source: | |
e505224d PB |
2613 | |
2614 | @example | |
b857d956 | 2615 | class vis @{ |
6fe91f2c | 2616 | private: |
b857d956 | 2617 | int priv; |
e505224d | 2618 | protected: |
b857d956 | 2619 | char prot; |
e505224d | 2620 | public: |
b857d956 | 2621 | float pub; |
e505224d PB |
2622 | @}; |
2623 | @end example | |
2624 | ||
899bafeb | 2625 | @noindent |
b857d956 | 2626 | generates the following stab: |
e505224d | 2627 | |
b857d956 JK |
2628 | @example |
2629 | # @r{128 is N_LSYM} | |
2630 | .stabs "vis:T19=s12priv:/01,0,32;prot:/12,32,8;pub:12,64,32;;",128,0,0,0 | |
2631 | @end example | |
e505224d | 2632 | |
b857d956 JK |
2633 | @samp{vis:T19=s12} indicates that type number 19 is a 12 byte structure |
2634 | named @code{vis} The @code{priv} field has public visibility | |
2635 | (@samp{/0}), type int (@samp{1}), and offset and size @samp{,0,32;}. | |
2636 | The @code{prot} field has protected visibility (@samp{/1}), type char | |
2637 | (@samp{2}) and offset and size @samp{,32,8;}. The @code{pub} field has | |
2638 | type float (@samp{12}), and offset and size @samp{,64,32;}. | |
e505224d PB |
2639 | |
2640 | Protections for member functions are signified by one digit embeded in | |
2641 | the field part of the stab describing the method. The digit is 0 if | |
2642 | private, 1 if protected and 2 if public. Consider the C++ class | |
2643 | definition below: | |
2644 | ||
2645 | @example | |
2646 | class all_methods @{ | |
2647 | private: | |
139741da | 2648 | int priv_meth(int in)@{return in;@}; |
e505224d | 2649 | protected: |
139741da | 2650 | char protMeth(char in)@{return in;@}; |
e505224d | 2651 | public: |
139741da | 2652 | float pubMeth(float in)@{return in;@}; |
e505224d PB |
2653 | @}; |
2654 | @end example | |
2655 | ||
2656 | It generates the following stab. The digit in question is to the left | |
6fe91f2c | 2657 | of an @samp{A} in each case. Notice also that in this case two symbol |
e505224d PB |
2658 | descriptors apply to the class name struct tag and struct type. |
2659 | ||
899bafeb | 2660 | @display |
e505224d | 2661 | .stabs "class_name:sym_desc(struct tag&type)type_def(21)= |
139741da RP |
2662 | sym_desc(struct)struct_bytes(1) |
2663 | meth_name::type_def(22)=sym_desc(method)returning(int); | |
2664 | :args(int);protection(private)modifier(normal)virtual(no); | |
2665 | meth_name::type_def(23)=sym_desc(method)returning(char); | |
2666 | :args(char);protection(protected)modifier(normal)virual(no); | |
2667 | meth_name::type_def(24)=sym_desc(method)returning(float); | |
2668 | :args(float);protection(public)modifier(normal)virtual(no);;", | |
2669 | N_LSYM,NIL,NIL,NIL | |
899bafeb | 2670 | @end display |
6fe91f2c | 2671 | |
899bafeb | 2672 | @smallexample |
e505224d | 2673 | .stabs "all_methods:Tt21=s1priv_meth::22=##1;:i;0A.;protMeth::23=##2;:c;1A.; |
139741da | 2674 | pubMeth::24=##12;:f;2A.;;",128,0,0,0 |
899bafeb | 2675 | @end smallexample |
e505224d | 2676 | |
bf9d2537 DM |
2677 | @node Method Modifiers |
2678 | @section Method Modifiers (@code{const}, @code{volatile}, @code{const volatile}) | |
e505224d PB |
2679 | |
2680 | << based on a6.C >> | |
2681 | ||
2682 | In the class example described above all the methods have the normal | |
2683 | modifier. This method modifier information is located just after the | |
2684 | protection information for the method. This field has four possible | |
6fe91f2c DM |
2685 | character values. Normal methods use @samp{A}, const methods use |
2686 | @samp{B}, volatile methods use @samp{C}, and const volatile methods use | |
2687 | @samp{D}. Consider the class definition below: | |
e505224d PB |
2688 | |
2689 | @example | |
2690 | class A @{ | |
2691 | public: | |
139741da RP |
2692 | int ConstMeth (int arg) const @{ return arg; @}; |
2693 | char VolatileMeth (char arg) volatile @{ return arg; @}; | |
2694 | float ConstVolMeth (float arg) const volatile @{return arg; @}; | |
e505224d PB |
2695 | @}; |
2696 | @end example | |
2697 | ||
2698 | This class is described by the following stab: | |
2699 | ||
899bafeb | 2700 | @display |
e505224d | 2701 | .stabs "class(A):sym_desc(struct)type_def(20)=type_desc(struct)struct_bytes(1) |
139741da RP |
2702 | meth_name(ConstMeth)::type_def(21)sym_desc(method) |
2703 | returning(int);:arg(int);protection(public)modifier(const)virtual(no); | |
2704 | meth_name(VolatileMeth)::type_def(22)=sym_desc(method) | |
2705 | returning(char);:arg(char);protection(public)modifier(volatile)virt(no) | |
2706 | meth_name(ConstVolMeth)::type_def(23)=sym_desc(method) | |
2707 | returning(float);:arg(float);protection(public)modifer(const volatile) | |
2708 | virtual(no);;", @dots{} | |
899bafeb | 2709 | @end display |
6fe91f2c | 2710 | |
899bafeb | 2711 | @example |
e505224d | 2712 | .stabs "A:T20=s1ConstMeth::21=##1;:i;2B.;VolatileMeth::22=##2;:c;2C.; |
139741da | 2713 | ConstVolMeth::23=##12;:f;2D.;;",128,0,0,0 |
612dbd4c | 2714 | @end example |
e505224d | 2715 | |
bf9d2537 DM |
2716 | @node Virtual Methods |
2717 | @section Virtual Methods | |
e505224d | 2718 | |
6fe91f2c | 2719 | << The following examples are based on a4.C >> |
e505224d PB |
2720 | |
2721 | The presence of virtual methods in a class definition adds additional | |
2722 | data to the class description. The extra data is appended to the | |
2723 | description of the virtual method and to the end of the class | |
2724 | description. Consider the class definition below: | |
2725 | ||
2726 | @example | |
2727 | class A @{ | |
2728 | public: | |
139741da RP |
2729 | int Adat; |
2730 | virtual int A_virt (int arg) @{ return arg; @}; | |
e505224d PB |
2731 | @}; |
2732 | @end example | |
6fe91f2c | 2733 | |
e505224d PB |
2734 | This results in the stab below describing class A. It defines a new |
2735 | type (20) which is an 8 byte structure. The first field of the class | |
6fe91f2c DM |
2736 | struct is @samp{Adat}, an integer, starting at structure offset 0 and |
2737 | occupying 32 bits. | |
e505224d PB |
2738 | |
2739 | The second field in the class struct is not explicitly defined by the | |
2740 | C++ class definition but is implied by the fact that the class | |
2741 | contains a virtual method. This field is the vtable pointer. The | |
6fe91f2c | 2742 | name of the vtable pointer field starts with @samp{$vf} and continues with a |
e505224d PB |
2743 | type reference to the class it is part of. In this example the type |
2744 | reference for class A is 20 so the name of its vtable pointer field is | |
6fe91f2c | 2745 | @samp{$vf20}, followed by the usual colon. |
e505224d PB |
2746 | |
2747 | Next there is a type definition for the vtable pointer type (21). | |
6fe91f2c | 2748 | This is in turn defined as a pointer to another new type (22). |
e505224d PB |
2749 | |
2750 | Type 22 is the vtable itself, which is defined as an array, indexed by | |
6aa83a79 JG |
2751 | a range of integers between 0 and 1, and whose elements are of type |
2752 | 17. Type 17 was the vtable record type defined by the boilerplate C++ | |
2753 | type definitions, as shown earlier. | |
e505224d PB |
2754 | |
2755 | The bit offset of the vtable pointer field is 32. The number of bits | |
2756 | in the field are not specified when the field is a vtable pointer. | |
6fe91f2c DM |
2757 | |
2758 | Next is the method definition for the virtual member function @code{A_virt}. | |
e505224d PB |
2759 | Its description starts out using the same format as the non-virtual |
2760 | member functions described above, except instead of a dot after the | |
6fe91f2c | 2761 | @samp{A} there is an asterisk, indicating that the function is virtual. |
e505224d | 2762 | Since is is virtual some addition information is appended to the end |
6fe91f2c | 2763 | of the method description. |
e505224d PB |
2764 | |
2765 | The first number represents the vtable index of the method. This is a | |
2766 | 32 bit unsigned number with the high bit set, followed by a | |
2767 | semi-colon. | |
2768 | ||
2769 | The second number is a type reference to the first base class in the | |
2770 | inheritence hierarchy defining the virtual member function. In this | |
2771 | case the class stab describes a base class so the virtual function is | |
2772 | not overriding any other definition of the method. Therefore the | |
2773 | reference is to the type number of the class that the stab is | |
6fe91f2c | 2774 | describing (20). |
e505224d PB |
2775 | |
2776 | This is followed by three semi-colons. One marks the end of the | |
2777 | current sub-section, one marks the end of the method field, and the | |
2778 | third marks the end of the struct definition. | |
2779 | ||
2780 | For classes containing virtual functions the very last section of the | |
2781 | string part of the stab holds a type reference to the first base | |
6fe91f2c | 2782 | class. This is preceeded by @samp{~%} and followed by a final semi-colon. |
e505224d | 2783 | |
899bafeb | 2784 | @display |
e505224d | 2785 | .stabs "class_name(A):type_def(20)=sym_desc(struct)struct_bytes(8) |
139741da RP |
2786 | field_name(Adat):type_ref(int),bit_offset(0),field_bits(32); |
2787 | field_name(A virt func ptr):type_def(21)=type_desc(ptr to)type_def(22)= | |
6aa83a79 | 2788 | sym_desc(array)index_type_ref(range of int from 0 to 1); |
6fe91f2c | 2789 | elem_type_ref(vtbl elem type), |
139741da RP |
2790 | bit_offset(32); |
2791 | meth_name(A_virt)::typedef(23)=sym_desc(method)returning(int); | |
2792 | :arg_type(int),protection(public)normal(yes)virtual(yes) | |
2793 | vtable_index(1);class_first_defining(A);;;~%first_base(A);", | |
2794 | N_LSYM,NIL,NIL,NIL | |
899bafeb | 2795 | @end display |
e505224d | 2796 | |
3d4cf720 | 2797 | @c FIXME: bogus line break. |
899bafeb | 2798 | @example |
3d4cf720 | 2799 | .stabs "A:t20=s8Adat:1,0,32;$vf20:21=*22=ar1;0;1;17,32; |
6fe91f2c | 2800 | A_virt::23=##1;:i;2A*-2147483647;20;;;~%20;",128,0,0,0 |
612dbd4c | 2801 | @end example |
e505224d | 2802 | |
2dd00294 JG |
2803 | @node Inheritence |
2804 | @section Inheritence | |
e505224d PB |
2805 | |
2806 | Stabs describing C++ derived classes include additional sections that | |
2807 | describe the inheritence hierarchy of the class. A derived class stab | |
2808 | also encodes the number of base classes. For each base class it tells | |
2809 | if the base class is virtual or not, and if the inheritence is private | |
2810 | or public. It also gives the offset into the object of the portion of | |
6fe91f2c | 2811 | the object corresponding to each base class. |
e505224d PB |
2812 | |
2813 | This additional information is embeded in the class stab following the | |
2814 | number of bytes in the struct. First the number of base classes | |
6fe91f2c | 2815 | appears bracketed by an exclamation point and a comma. |
e505224d | 2816 | |
b857d956 JK |
2817 | Then for each base type there repeats a series: a virtual character, a |
2818 | visibilty character, a number, a comma, another number, and a | |
2819 | semi-colon. | |
e505224d | 2820 | |
b857d956 JK |
2821 | The virtual character is @samp{1} if the base class is virtual and |
2822 | @samp{0} if not. The visibility character is @samp{2} if the derivation | |
2823 | is public, @samp{1} if it is protected, and @samp{0} if it is private. | |
2824 | Debuggers should ignore virtual or visibility characters they do not | |
2825 | recognize, and assume a reasonable default (such as public and | |
2826 | non-virtual) (GDB 4.11 does not, but this should be fixed in the next | |
2827 | GDB release). | |
e505224d | 2828 | |
b857d956 JK |
2829 | The number following the virtual and visibility characters is the offset |
2830 | from the start of the object to the part of the object pertaining to the | |
2831 | base class. | |
e505224d PB |
2832 | |
2833 | After the comma, the second number is a type_descriptor for the base | |
2834 | type. Finally a semi-colon ends the series, which repeats for each | |
2835 | base class. | |
2836 | ||
6fe91f2c DM |
2837 | The source below defines three base classes @code{A}, @code{B}, and |
2838 | @code{C} and the derived class @code{D}. | |
e505224d PB |
2839 | |
2840 | ||
2841 | @example | |
2842 | class A @{ | |
2843 | public: | |
139741da RP |
2844 | int Adat; |
2845 | virtual int A_virt (int arg) @{ return arg; @}; | |
e505224d PB |
2846 | @}; |
2847 | ||
2848 | class B @{ | |
2849 | public: | |
6fe91f2c | 2850 | int B_dat; |
139741da | 2851 | virtual int B_virt (int arg) @{return arg; @}; |
6fe91f2c | 2852 | @}; |
e505224d PB |
2853 | |
2854 | class C @{ | |
6fe91f2c | 2855 | public: |
139741da | 2856 | int Cdat; |
6fe91f2c | 2857 | virtual int C_virt (int arg) @{return arg; @}; |
e505224d PB |
2858 | @}; |
2859 | ||
2860 | class D : A, virtual B, public C @{ | |
2861 | public: | |
139741da RP |
2862 | int Ddat; |
2863 | virtual int A_virt (int arg ) @{ return arg+1; @}; | |
2864 | virtual int B_virt (int arg) @{ return arg+2; @}; | |
2865 | virtual int C_virt (int arg) @{ return arg+3; @}; | |
2866 | virtual int D_virt (int arg) @{ return arg; @}; | |
e505224d PB |
2867 | @}; |
2868 | @end example | |
2869 | ||
2870 | Class stabs similar to the ones described earlier are generated for | |
6fe91f2c | 2871 | each base class. |
e505224d | 2872 | |
5bc927fb RP |
2873 | @c FIXME!!! the linebreaks in the following example probably make the |
2874 | @c examples literally unusable, but I don't know any other way to get | |
2875 | @c them on the page. | |
63cef7d7 JK |
2876 | @c One solution would be to put some of the type definitions into |
2877 | @c separate stabs, even if that's not exactly what the compiler actually | |
2878 | @c emits. | |
899bafeb | 2879 | @smallexample |
5bc927fb RP |
2880 | .stabs "A:T20=s8Adat:1,0,32;$vf20:21=*22=ar1;0;1;17,32; |
2881 | A_virt::23=##1;:i;2A*-2147483647;20;;;~%20;",128,0,0,0 | |
e505224d | 2882 | |
5bc927fb RP |
2883 | .stabs "B:Tt25=s8Bdat:1,0,32;$vf25:21,32;B_virt::26=##1; |
2884 | :i;2A*-2147483647;25;;;~%25;",128,0,0,0 | |
e505224d | 2885 | |
5bc927fb RP |
2886 | .stabs "C:Tt28=s8Cdat:1,0,32;$vf28:21,32;C_virt::29=##1; |
2887 | :i;2A*-2147483647;28;;;~%28;",128,0,0,0 | |
899bafeb | 2888 | @end smallexample |
e505224d | 2889 | |
6fe91f2c | 2890 | In the stab describing derived class @code{D} below, the information about |
e505224d PB |
2891 | the derivation of this class is encoded as follows. |
2892 | ||
899bafeb | 2893 | @display |
e505224d | 2894 | .stabs "derived_class_name:symbol_descriptors(struct tag&type)= |
139741da RP |
2895 | type_descriptor(struct)struct_bytes(32)!num_bases(3), |
2896 | base_virtual(no)inheritence_public(no)base_offset(0), | |
2897 | base_class_type_ref(A); | |
2898 | base_virtual(yes)inheritence_public(no)base_offset(NIL), | |
2899 | base_class_type_ref(B); | |
2900 | base_virtual(no)inheritence_public(yes)base_offset(64), | |
2901 | base_class_type_ref(C); @dots{} | |
899bafeb | 2902 | @end display |
6fe91f2c | 2903 | |
5bc927fb | 2904 | @c FIXME! fake linebreaks. |
899bafeb | 2905 | @smallexample |
5bc927fb RP |
2906 | .stabs "D:Tt31=s32!3,000,20;100,25;0264,28;$vb25:24,128;Ddat: |
2907 | 1,160,32;A_virt::32=##1;:i;2A*-2147483647;20;;B_virt: | |
2908 | :32:i;2A*-2147483647;25;;C_virt::32:i;2A*-2147483647; | |
2909 | 28;;D_virt::32:i;2A*-2147483646;31;;;~%20;",128,0,0,0 | |
899bafeb | 2910 | @end smallexample |
e505224d | 2911 | |
bf9d2537 DM |
2912 | @node Virtual Base Classes |
2913 | @section Virtual Base Classes | |
e505224d | 2914 | |
dd8126d9 JK |
2915 | A derived class object consists of a concatination in memory of the data |
2916 | areas defined by each base class, starting with the leftmost and ending | |
2917 | with the rightmost in the list of base classes. The exception to this | |
2918 | rule is for virtual inheritence. In the example above, class @code{D} | |
2919 | inherits virtually from base class @code{B}. This means that an | |
2920 | instance of a @code{D} object will not contain its own @code{B} part but | |
2921 | merely a pointer to a @code{B} part, known as a virtual base pointer. | |
e505224d PB |
2922 | |
2923 | In a derived class stab, the base offset part of the derivation | |
2924 | information, described above, shows how the base class parts are | |
dd8126d9 JK |
2925 | ordered. The base offset for a virtual base class is always given as 0. |
2926 | Notice that the base offset for @code{B} is given as 0 even though | |
2927 | @code{B} is not the first base class. The first base class @code{A} | |
2928 | starts at offset 0. | |
e505224d | 2929 | |
6fe91f2c DM |
2930 | The field information part of the stab for class @code{D} describes the field |
2931 | which is the pointer to the virtual base class @code{B}. The vbase pointer | |
2932 | name is @samp{$vb} followed by a type reference to the virtual base class. | |
2933 | Since the type id for @code{B} in this example is 25, the vbase pointer name | |
2934 | is @samp{$vb25}. | |
e505224d | 2935 | |
5bc927fb | 2936 | @c FIXME!! fake linebreaks below |
899bafeb | 2937 | @smallexample |
5bc927fb RP |
2938 | .stabs "D:Tt31=s32!3,000,20;100,25;0264,28;$vb25:24,128;Ddat:1, |
2939 | 160,32;A_virt::32=##1;:i;2A*-2147483647;20;;B_virt::32:i; | |
2940 | 2A*-2147483647;25;;C_virt::32:i;2A*-2147483647;28;;D_virt: | |
2941 | :32:i;2A*-2147483646;31;;;~%20;",128,0,0,0 | |
899bafeb | 2942 | @end smallexample |
e505224d PB |
2943 | |
2944 | Following the name and a semicolon is a type reference describing the | |
2945 | type of the virtual base class pointer, in this case 24. Type 24 was | |
6fe91f2c DM |
2946 | defined earlier as the type of the @code{B} class @code{this} pointer. The |
2947 | @code{this} pointer for a class is a pointer to the class type. | |
e505224d | 2948 | |
899bafeb | 2949 | @example |
c2dc518b | 2950 | .stabs "this:P24=*25=xsB:",64,0,0,8 |
899bafeb | 2951 | @end example |
e505224d PB |
2952 | |
2953 | Finally the field offset part of the vbase pointer field description | |
6fe91f2c DM |
2954 | shows that the vbase pointer is the first field in the @code{D} object, |
2955 | before any data fields defined by the class. The layout of a @code{D} | |
2956 | class object is a follows, @code{Adat} at 0, the vtable pointer for | |
2957 | @code{A} at 32, @code{Cdat} at 64, the vtable pointer for C at 96, the | |
2958 | virtual base pointer for @code{B} at 128, and @code{Ddat} at 160. | |
e505224d PB |
2959 | |
2960 | ||
bf9d2537 DM |
2961 | @node Static Members |
2962 | @section Static Members | |
e505224d | 2963 | |
446e5d80 JG |
2964 | The data area for a class is a concatenation of the space used by the |
2965 | data members of the class. If the class has virtual methods, a vtable | |
e505224d | 2966 | pointer follows the class data. The field offset part of each field |
446e5d80 | 2967 | description in the class stab shows this ordering. |
e505224d | 2968 | |
446e5d80 | 2969 | << How is this reflected in stabs? See Cygnus bug #677 for some info. >> |
e505224d | 2970 | |
bf9d2537 DM |
2971 | @node Stab Types |
2972 | @appendix Table of Stab Types | |
e505224d | 2973 | |
0a95c18c JK |
2974 | The following are all the possible values for the stab type field, for |
2975 | @code{a.out} files, in numeric order. This does not apply to XCOFF, but | |
e89d48dd JL |
2976 | it does apply to stabs in ELF and stabs in SOM. Stabs in ECOFF use these |
2977 | values but add 0x8f300 to distinguish them from non-stab symbols. | |
e505224d | 2978 | |
6fe91f2c DM |
2979 | The symbolic names are defined in the file @file{include/aout/stabs.def}. |
2980 | ||
2981 | @menu | |
bf9d2537 DM |
2982 | * Non-Stab Symbol Types:: Types from 0 to 0x1f |
2983 | * Stab Symbol Types:: Types from 0x20 to 0xff | |
6fe91f2c DM |
2984 | @end menu |
2985 | ||
bf9d2537 DM |
2986 | @node Non-Stab Symbol Types |
2987 | @appendixsec Non-Stab Symbol Types | |
6fe91f2c DM |
2988 | |
2989 | The following types are used by the linker and assembler, not by stab | |
2990 | directives. Since this document does not attempt to describe aspects of | |
2991 | object file format other than the debugging format, no details are | |
2992 | given. | |
e505224d | 2993 | |
3d4cf720 JK |
2994 | @c Try to get most of these to fit on a single line. |
2995 | @iftex | |
2996 | @tableindent=1.5in | |
2997 | @end iftex | |
e505224d | 2998 | |
3d4cf720 | 2999 | @table @code |
6fe91f2c | 3000 | @item 0x0 N_UNDF |
3d4cf720 | 3001 | Undefined symbol |
e505224d | 3002 | |
6fe91f2c | 3003 | @item 0x2 N_ABS |
3d4cf720 | 3004 | File scope absolute symbol |
e505224d | 3005 | |
6fe91f2c | 3006 | @item 0x3 N_ABS | N_EXT |
3d4cf720 JK |
3007 | External absolute symbol |
3008 | ||
6fe91f2c | 3009 | @item 0x4 N_TEXT |
3d4cf720 JK |
3010 | File scope text symbol |
3011 | ||
6fe91f2c | 3012 | @item 0x5 N_TEXT | N_EXT |
3d4cf720 JK |
3013 | External text symbol |
3014 | ||
6fe91f2c | 3015 | @item 0x6 N_DATA |
3d4cf720 JK |
3016 | File scope data symbol |
3017 | ||
6fe91f2c | 3018 | @item 0x7 N_DATA | N_EXT |
3d4cf720 JK |
3019 | External data symbol |
3020 | ||
6fe91f2c | 3021 | @item 0x8 N_BSS |
3d4cf720 JK |
3022 | File scope BSS symbol |
3023 | ||
6fe91f2c | 3024 | @item 0x9 N_BSS | N_EXT |
3d4cf720 JK |
3025 | External BSS symbol |
3026 | ||
6fe91f2c DM |
3027 | @item 0x0c N_FN_SEQ |
3028 | Same as @code{N_FN}, for Sequent compilers | |
3d4cf720 | 3029 | |
6fe91f2c | 3030 | @item 0x0a N_INDR |
3d4cf720 JK |
3031 | Symbol is indirected to another symbol |
3032 | ||
6fe91f2c | 3033 | @item 0x12 N_COMM |
dd8126d9 | 3034 | Common---visible after shared library dynamic link |
3d4cf720 | 3035 | |
6fe91f2c | 3036 | @item 0x14 N_SETA |
59502c19 | 3037 | @itemx 0x15 N_SETA | N_EXT |
3d4cf720 JK |
3038 | Absolute set element |
3039 | ||
6fe91f2c | 3040 | @item 0x16 N_SETT |
59502c19 | 3041 | @itemx 0x17 N_SETT | N_EXT |
3d4cf720 JK |
3042 | Text segment set element |
3043 | ||
6fe91f2c | 3044 | @item 0x18 N_SETD |
59502c19 | 3045 | @itemx 0x19 N_SETD | N_EXT |
3d4cf720 JK |
3046 | Data segment set element |
3047 | ||
6fe91f2c | 3048 | @item 0x1a N_SETB |
59502c19 | 3049 | @itemx 0x1b N_SETB | N_EXT |
3d4cf720 JK |
3050 | BSS segment set element |
3051 | ||
6fe91f2c | 3052 | @item 0x1c N_SETV |
59502c19 | 3053 | @itemx 0x1d N_SETV | N_EXT |
3d4cf720 JK |
3054 | Pointer to set vector |
3055 | ||
6fe91f2c | 3056 | @item 0x1e N_WARNING |
3d4cf720 JK |
3057 | Print a warning message during linking |
3058 | ||
6fe91f2c DM |
3059 | @item 0x1f N_FN |
3060 | File name of a @file{.o} file | |
3d4cf720 JK |
3061 | @end table |
3062 | ||
bf9d2537 DM |
3063 | @node Stab Symbol Types |
3064 | @appendixsec Stab Symbol Types | |
6fe91f2c | 3065 | |
3d4cf720 JK |
3066 | The following symbol types indicate that this is a stab. This is the |
3067 | full list of stab numbers, including stab types that are used in | |
3068 | languages other than C. | |
3069 | ||
3070 | @table @code | |
3071 | @item 0x20 N_GSYM | |
bf9d2537 | 3072 | Global symbol; see @ref{Global Variables}. |
3d4cf720 JK |
3073 | |
3074 | @item 0x22 N_FNAME | |
43603088 | 3075 | Function name (for BSD Fortran); see @ref{Procedures}. |
3d4cf720 | 3076 | |
24dcc707 JK |
3077 | @item 0x24 N_FUN |
3078 | Function name (@pxref{Procedures}) or text segment variable | |
3079 | (@pxref{Statics}). | |
3d4cf720 | 3080 | |
24dcc707 | 3081 | @item 0x26 N_STSYM |
6fe91f2c | 3082 | Data segment file-scope variable; see @ref{Statics}. |
3d4cf720 | 3083 | |
24dcc707 | 3084 | @item 0x28 N_LCSYM |
6fe91f2c | 3085 | BSS segment file-scope variable; see @ref{Statics}. |
3d4cf720 | 3086 | |
6fe91f2c | 3087 | @item 0x2a N_MAIN |
bf9d2537 | 3088 | Name of main routine; see @ref{Main Program}. |
3d4cf720 | 3089 | |
ded6bcab | 3090 | @item 0x2c N_ROSYM |
6fe91f2c | 3091 | Variable in @code{.rodata} section; see @ref{Statics}. |
ded6bcab | 3092 | |
6fe91f2c DM |
3093 | @item 0x30 N_PC |
3094 | Global symbol (for Pascal); see @ref{N_PC}. | |
3d4cf720 | 3095 | |
6fe91f2c DM |
3096 | @item 0x32 N_NSYMS |
3097 | Number of symbols (according to Ultrix V4.0); see @ref{N_NSYMS}. | |
3d4cf720 | 3098 | |
6fe91f2c DM |
3099 | @item 0x34 N_NOMAP |
3100 | No DST map; see @ref{N_NOMAP}. | |
3d4cf720 | 3101 | |
ded6bcab JK |
3102 | @c FIXME: describe this solaris feature in the body of the text (see |
3103 | @c comments in include/aout/stab.def). | |
3104 | @item 0x38 N_OBJ | |
3105 | Object file (Solaris2). | |
3106 | ||
3107 | @c See include/aout/stab.def for (a little) more info. | |
3108 | @item 0x3c N_OPT | |
3109 | Debugger options (Solaris2). | |
3110 | ||
6fe91f2c | 3111 | @item 0x40 N_RSYM |
bf9d2537 | 3112 | Register variable; see @ref{Register Variables}. |
3d4cf720 | 3113 | |
6fe91f2c DM |
3114 | @item 0x42 N_M2C |
3115 | Modula-2 compilation unit; see @ref{N_M2C}. | |
3d4cf720 | 3116 | |
6fe91f2c | 3117 | @item 0x44 N_SLINE |
bf9d2537 | 3118 | Line number in text segment; see @ref{Line Numbers}. |
3d4cf720 | 3119 | |
6fe91f2c | 3120 | @item 0x46 N_DSLINE |
bf9d2537 | 3121 | Line number in data segment; see @ref{Line Numbers}. |
3d4cf720 | 3122 | |
6fe91f2c | 3123 | @item 0x48 N_BSLINE |
bf9d2537 | 3124 | Line number in bss segment; see @ref{Line Numbers}. |
3d4cf720 | 3125 | |
6fe91f2c DM |
3126 | @item 0x48 N_BROWS |
3127 | Sun source code browser, path to @file{.cb} file; see @ref{N_BROWS}. | |
3d4cf720 | 3128 | |
6fe91f2c DM |
3129 | @item 0x4a N_DEFD |
3130 | GNU Modula2 definition module dependency; see @ref{N_DEFD}. | |
3d4cf720 | 3131 | |
ded6bcab JK |
3132 | @item 0x4c N_FLINE |
3133 | Function start/body/end line numbers (Solaris2). | |
3134 | ||
6fe91f2c DM |
3135 | @item 0x50 N_EHDECL |
3136 | GNU C++ exception variable; see @ref{N_EHDECL}. | |
3d4cf720 | 3137 | |
6fe91f2c DM |
3138 | @item 0x50 N_MOD2 |
3139 | Modula2 info "for imc" (according to Ultrix V4.0); see @ref{N_MOD2}. | |
3d4cf720 | 3140 | |
6fe91f2c DM |
3141 | @item 0x54 N_CATCH |
3142 | GNU C++ @code{catch} clause; see @ref{N_CATCH}. | |
3d4cf720 | 3143 | |
6fe91f2c DM |
3144 | @item 0x60 N_SSYM |
3145 | Structure of union element; see @ref{N_SSYM}. | |
3d4cf720 | 3146 | |
ded6bcab JK |
3147 | @item 0x62 N_ENDM |
3148 | Last stab for module (Solaris2). | |
3149 | ||
6fe91f2c | 3150 | @item 0x64 N_SO |
bf9d2537 | 3151 | Path and name of source file; see @ref{Source Files}. |
3d4cf720 | 3152 | |
935d305d | 3153 | @item 0x80 N_LSYM |
bf9d2537 | 3154 | Stack variable (@pxref{Stack Variables}) or type (@pxref{Typedefs}). |
3d4cf720 | 3155 | |
6fe91f2c | 3156 | @item 0x82 N_BINCL |
bf9d2537 | 3157 | Beginning of an include file (Sun only); see @ref{Include Files}. |
3d4cf720 | 3158 | |
6fe91f2c | 3159 | @item 0x84 N_SOL |
bf9d2537 | 3160 | Name of include file; see @ref{Include Files}. |
3d4cf720 | 3161 | |
6fe91f2c DM |
3162 | @item 0xa0 N_PSYM |
3163 | Parameter variable; see @ref{Parameters}. | |
3d4cf720 | 3164 | |
6fe91f2c | 3165 | @item 0xa2 N_EINCL |
bf9d2537 | 3166 | End of an include file; see @ref{Include Files}. |
3d4cf720 | 3167 | |
6fe91f2c DM |
3168 | @item 0xa4 N_ENTRY |
3169 | Alternate entry point; see @ref{N_ENTRY}. | |
3d4cf720 | 3170 | |
6fe91f2c | 3171 | @item 0xc0 N_LBRAC |
bf9d2537 | 3172 | Beginning of a lexical block; see @ref{Block Structure}. |
3d4cf720 | 3173 | |
6fe91f2c | 3174 | @item 0xc2 N_EXCL |
bf9d2537 | 3175 | Place holder for a deleted include file; see @ref{Include Files}. |
3d4cf720 | 3176 | |
6fe91f2c DM |
3177 | @item 0xc4 N_SCOPE |
3178 | Modula2 scope information (Sun linker); see @ref{N_SCOPE}. | |
3d4cf720 | 3179 | |
6fe91f2c | 3180 | @item 0xe0 N_RBRAC |
bf9d2537 | 3181 | End of a lexical block; see @ref{Block Structure}. |
3d4cf720 | 3182 | |
6fe91f2c | 3183 | @item 0xe2 N_BCOMM |
bf9d2537 | 3184 | Begin named common block; see @ref{Common Blocks}. |
3d4cf720 | 3185 | |
6fe91f2c | 3186 | @item 0xe4 N_ECOMM |
bf9d2537 | 3187 | End named common block; see @ref{Common Blocks}. |
3d4cf720 | 3188 | |
6fe91f2c | 3189 | @item 0xe8 N_ECOML |
bf9d2537 | 3190 | Member of a common block; see @ref{Common Blocks}. |
3d4cf720 | 3191 | |
ded6bcab JK |
3192 | @c FIXME: How does this really work? Move it to main body of document. |
3193 | @item 0xea N_WITH | |
3194 | Pascal @code{with} statement: type,,0,0,offset (Solaris2). | |
3195 | ||
6fe91f2c DM |
3196 | @item 0xf0 N_NBTEXT |
3197 | Gould non-base registers; see @ref{Gould}. | |
3d4cf720 | 3198 | |
6fe91f2c DM |
3199 | @item 0xf2 N_NBDATA |
3200 | Gould non-base registers; see @ref{Gould}. | |
3d4cf720 JK |
3201 | |
3202 | @item 0xf4 N_NBBSS | |
6fe91f2c | 3203 | Gould non-base registers; see @ref{Gould}. |
3d4cf720 | 3204 | |
6fe91f2c DM |
3205 | @item 0xf6 N_NBSTS |
3206 | Gould non-base registers; see @ref{Gould}. | |
3d4cf720 | 3207 | |
6fe91f2c DM |
3208 | @item 0xf8 N_NBLCS |
3209 | Gould non-base registers; see @ref{Gould}. | |
3d4cf720 JK |
3210 | @end table |
3211 | ||
3212 | @c Restore the default table indent | |
3213 | @iftex | |
3214 | @tableindent=.8in | |
3215 | @end iftex | |
e505224d | 3216 | |
bf9d2537 DM |
3217 | @node Symbol Descriptors |
3218 | @appendix Table of Symbol Descriptors | |
e505224d | 3219 | |
0a95c18c | 3220 | The symbol descriptor is the character which follows the colon in many |
bf9d2537 | 3221 | stabs, and which tells what kind of stab it is. @xref{String Field}, |
0a95c18c | 3222 | for more information about their use. |
6fe91f2c | 3223 | |
ed9708e2 | 3224 | @c Please keep this alphabetical |
497e44a5 | 3225 | @table @code |
466bdeb2 JK |
3226 | @c In TeX, this looks great, digit is in italics. But makeinfo insists |
3227 | @c on putting it in `', not realizing that @var should override @code. | |
3228 | @c I don't know of any way to make makeinfo do the right thing. Seems | |
3229 | @c like a makeinfo bug to me. | |
3230 | @item @var{digit} | |
8c59ee11 JK |
3231 | @itemx ( |
3232 | @itemx - | |
bf9d2537 | 3233 | Variable on the stack; see @ref{Stack Variables}. |
497e44a5 | 3234 | |
397f9dcd JK |
3235 | @item : |
3236 | C++ nested symbol; see @xref{Nested Symbols} | |
3237 | ||
6897f9ec | 3238 | @item a |
bf9d2537 | 3239 | Parameter passed by reference in register; see @ref{Reference Parameters}. |
6897f9ec | 3240 | |
408f6c34 | 3241 | @item b |
f19027a6 | 3242 | Based variable; see @ref{Based Variables}. |
408f6c34 | 3243 | |
6897f9ec | 3244 | @item c |
6fe91f2c | 3245 | Constant; see @ref{Constants}. |
6897f9ec | 3246 | |
ed9708e2 | 3247 | @item C |
43603088 | 3248 | Conformant array bound (Pascal, maybe other languages); @ref{Conformant |
bf9d2537 | 3249 | Arrays}. Name of a caught exception (GNU C++). These can be |
685a5e86 | 3250 | distinguished because the latter uses @code{N_CATCH} and the former uses |
8c59ee11 | 3251 | another symbol type. |
6897f9ec JK |
3252 | |
3253 | @item d | |
bf9d2537 | 3254 | Floating point register variable; see @ref{Register Variables}. |
6897f9ec JK |
3255 | |
3256 | @item D | |
bf9d2537 | 3257 | Parameter in floating point register; see @ref{Register Parameters}. |
ed9708e2 | 3258 | |
497e44a5 | 3259 | @item f |
6fe91f2c | 3260 | File scope function; see @ref{Procedures}. |
497e44a5 JK |
3261 | |
3262 | @item F | |
6fe91f2c | 3263 | Global function; see @ref{Procedures}. |
497e44a5 | 3264 | |
497e44a5 | 3265 | @item G |
bf9d2537 | 3266 | Global variable; see @ref{Global Variables}. |
497e44a5 | 3267 | |
ed9708e2 | 3268 | @item i |
bf9d2537 | 3269 | @xref{Register Parameters}. |
ed9708e2 | 3270 | |
6897f9ec | 3271 | @item I |
bf9d2537 | 3272 | Internal (nested) procedure; see @ref{Nested Procedures}. |
6897f9ec JK |
3273 | |
3274 | @item J | |
bf9d2537 | 3275 | Internal (nested) function; see @ref{Nested Procedures}. |
6897f9ec JK |
3276 | |
3277 | @item L | |
3278 | Label name (documented by AIX, no further information known). | |
3279 | ||
3280 | @item m | |
6fe91f2c | 3281 | Module; see @ref{Procedures}. |
6897f9ec | 3282 | |
ed9708e2 | 3283 | @item p |
6fe91f2c | 3284 | Argument list parameter; see @ref{Parameters}. |
ed9708e2 JK |
3285 | |
3286 | @item pP | |
3287 | @xref{Parameters}. | |
3288 | ||
3289 | @item pF | |
6fe91f2c | 3290 | Fortran Function parameter; see @ref{Parameters}. |
ed9708e2 JK |
3291 | |
3292 | @item P | |
1a8b5668 JK |
3293 | Unfortunately, three separate meanings have been independently invented |
3294 | for this symbol descriptor. At least the GNU and Sun uses can be | |
3295 | distinguished by the symbol type. Global Procedure (AIX) (symbol type | |
685a5e86 DM |
3296 | used unknown); see @ref{Procedures}. Register parameter (GNU) (symbol |
3297 | type @code{N_PSYM}); see @ref{Parameters}. Prototype of function | |
3298 | referenced by this file (Sun @code{acc}) (symbol type @code{N_FUN}). | |
6897f9ec JK |
3299 | |
3300 | @item Q | |
6fe91f2c | 3301 | Static Procedure; see @ref{Procedures}. |
6897f9ec JK |
3302 | |
3303 | @item R | |
bf9d2537 | 3304 | Register parameter; see @ref{Register Parameters}. |
ed9708e2 | 3305 | |
497e44a5 | 3306 | @item r |
bf9d2537 | 3307 | Register variable; see @ref{Register Variables}. |
497e44a5 JK |
3308 | |
3309 | @item S | |
6fe91f2c | 3310 | File scope variable; see @ref{Statics}. |
497e44a5 | 3311 | |
ed9708e2 | 3312 | @item t |
6fe91f2c | 3313 | Type name; see @ref{Typedefs}. |
ed9708e2 JK |
3314 | |
3315 | @item T | |
685a5e86 | 3316 | Enumeration, structure, or union tag; see @ref{Typedefs}. |
ed9708e2 JK |
3317 | |
3318 | @item v | |
bf9d2537 | 3319 | Parameter passed by reference; see @ref{Reference Parameters}. |
ed9708e2 | 3320 | |
497e44a5 | 3321 | @item V |
6fe91f2c | 3322 | Procedure scope static variable; see @ref{Statics}. |
497e44a5 | 3323 | |
6897f9ec | 3324 | @item x |
bf9d2537 | 3325 | Conformant array; see @ref{Conformant Arrays}. |
6897f9ec | 3326 | |
ed9708e2 | 3327 | @item X |
6fe91f2c | 3328 | Function return variable; see @ref{Parameters}. |
497e44a5 | 3329 | @end table |
e505224d | 3330 | |
bf9d2537 DM |
3331 | @node Type Descriptors |
3332 | @appendix Table of Type Descriptors | |
e505224d | 3333 | |
0a95c18c JK |
3334 | The type descriptor is the character which follows the type number and |
3335 | an equals sign. It specifies what kind of type is being defined. | |
bf9d2537 | 3336 | @xref{String Field}, for more information about their use. |
6fe91f2c | 3337 | |
6897f9ec | 3338 | @table @code |
8c59ee11 JK |
3339 | @item @var{digit} |
3340 | @itemx ( | |
bf9d2537 | 3341 | Type reference; see @ref{String Field}. |
8c59ee11 JK |
3342 | |
3343 | @item - | |
bf9d2537 | 3344 | Reference to builtin type; see @ref{Negative Type Numbers}. |
8c59ee11 JK |
3345 | |
3346 | @item # | |
6fe91f2c | 3347 | Method (C++); see @ref{Cplusplus}. |
6897f9ec JK |
3348 | |
3349 | @item * | |
bf9d2537 | 3350 | Pointer; see @ref{Miscellaneous Types}. |
8c59ee11 JK |
3351 | |
3352 | @item & | |
3353 | Reference (C++). | |
6897f9ec JK |
3354 | |
3355 | @item @@ | |
bf9d2537 | 3356 | Type Attributes (AIX); see @ref{String Field}. Member (class and variable) |
6fe91f2c | 3357 | type (GNU C++); see @ref{Cplusplus}. |
e505224d | 3358 | |
6897f9ec | 3359 | @item a |
6fe91f2c | 3360 | Array; see @ref{Arrays}. |
8c59ee11 JK |
3361 | |
3362 | @item A | |
6fe91f2c | 3363 | Open array; see @ref{Arrays}. |
8c59ee11 JK |
3364 | |
3365 | @item b | |
bf9d2537 DM |
3366 | Pascal space type (AIX); see @ref{Miscellaneous Types}. Builtin integer |
3367 | type (Sun); see @ref{Builtin Type Descriptors}. | |
8c59ee11 JK |
3368 | |
3369 | @item B | |
bf9d2537 | 3370 | Volatile-qualified type; see @ref{Miscellaneous Types}. |
8c59ee11 JK |
3371 | |
3372 | @item c | |
bf9d2537 | 3373 | Complex builtin type; see @ref{Builtin Type Descriptors}. |
8c59ee11 JK |
3374 | |
3375 | @item C | |
3376 | COBOL Picture type. See AIX documentation for details. | |
3377 | ||
3378 | @item d | |
bf9d2537 | 3379 | File type; see @ref{Miscellaneous Types}. |
8c59ee11 JK |
3380 | |
3381 | @item D | |
6fe91f2c | 3382 | N-dimensional dynamic array; see @ref{Arrays}. |
6897f9ec JK |
3383 | |
3384 | @item e | |
6fe91f2c | 3385 | Enumeration type; see @ref{Enumerations}. |
8c59ee11 JK |
3386 | |
3387 | @item E | |
6fe91f2c | 3388 | N-dimensional subarray; see @ref{Arrays}. |
6897f9ec JK |
3389 | |
3390 | @item f | |
bf9d2537 | 3391 | Function type; see @ref{Function Types}. |
a03f27c3 JK |
3392 | |
3393 | @item F | |
bf9d2537 | 3394 | Pascal function parameter; see @ref{Function Types} |
8c59ee11 JK |
3395 | |
3396 | @item g | |
bf9d2537 | 3397 | Builtin floating point type; see @ref{Builtin Type Descriptors}. |
8c59ee11 JK |
3398 | |
3399 | @item G | |
3400 | COBOL Group. See AIX documentation for details. | |
3401 | ||
3402 | @item i | |
bf9d2537 | 3403 | Imported type; see @ref{Cross-References}. |
8c59ee11 JK |
3404 | |
3405 | @item k | |
bf9d2537 | 3406 | Const-qualified type; see @ref{Miscellaneous Types}. |
8c59ee11 JK |
3407 | |
3408 | @item K | |
3409 | COBOL File Descriptor. See AIX documentation for details. | |
3410 | ||
a03f27c3 | 3411 | @item M |
bf9d2537 | 3412 | Multiple instance type; see @ref{Miscellaneous Types}. |
a03f27c3 | 3413 | |
8c59ee11 | 3414 | @item n |
6fe91f2c | 3415 | String type; see @ref{Strings}. |
8c59ee11 JK |
3416 | |
3417 | @item N | |
6fe91f2c | 3418 | Stringptr; see @ref{Strings}. |
8c59ee11 | 3419 | |
8c59ee11 | 3420 | @item o |
6fe91f2c | 3421 | Opaque type; see @ref{Typedefs}. |
8c59ee11 | 3422 | |
a03f27c3 | 3423 | @item p |
bf9d2537 | 3424 | Procedure; see @ref{Function Types}. |
a03f27c3 | 3425 | |
8c59ee11 | 3426 | @item P |
6fe91f2c | 3427 | Packed array; see @ref{Arrays}. |
6897f9ec JK |
3428 | |
3429 | @item r | |
6fe91f2c | 3430 | Range type; see @ref{Subranges}. |
8c59ee11 JK |
3431 | |
3432 | @item R | |
bf9d2537 DM |
3433 | Builtin floating type; see @ref{Builtin Type Descriptors} (Sun). Pascal |
3434 | subroutine parameter; see @ref{Function Types} (AIX). Detecting this | |
a03f27c3 JK |
3435 | conflict is possible with careful parsing (hint: a Pascal subroutine |
3436 | parameter type will always contain a comma, and a builtin type | |
3437 | descriptor never will). | |
6897f9ec JK |
3438 | |
3439 | @item s | |
6fe91f2c | 3440 | Structure type; see @ref{Structures}. |
8c59ee11 JK |
3441 | |
3442 | @item S | |
bf9d2537 | 3443 | Set type; see @ref{Miscellaneous Types}. |
6897f9ec JK |
3444 | |
3445 | @item u | |
6fe91f2c | 3446 | Union; see @ref{Unions}. |
8c59ee11 JK |
3447 | |
3448 | @item v | |
3449 | Variant record. This is a Pascal and Modula-2 feature which is like a | |
3450 | union within a struct in C. See AIX documentation for details. | |
3451 | ||
3452 | @item w | |
bf9d2537 | 3453 | Wide character; see @ref{Builtin Type Descriptors}. |
8c59ee11 JK |
3454 | |
3455 | @item x | |
bf9d2537 | 3456 | Cross-reference; see @ref{Cross-References}. |
6897f9ec | 3457 | |
8c59ee11 | 3458 | @item z |
6fe91f2c | 3459 | gstring; see @ref{Strings}. |
6897f9ec | 3460 | @end table |
e505224d | 3461 | |
bf9d2537 DM |
3462 | @node Expanded Reference |
3463 | @appendix Expanded Reference by Stab Type | |
e505224d | 3464 | |
685a5e86 | 3465 | @c FIXME: This appendix should go away; see N_PSYM or N_SO for an example. |
8c59ee11 | 3466 | |
3d4cf720 | 3467 | For a full list of stab types, and cross-references to where they are |
bf9d2537 | 3468 | described, see @ref{Stab Types}. This appendix just duplicates certain |
3d4cf720 JK |
3469 | information from the main body of this document; eventually the |
3470 | information will all be in one place. | |
8c59ee11 | 3471 | |
e505224d | 3472 | Format of an entry: |
6fe91f2c | 3473 | |
685a5e86 | 3474 | The first line is the symbol type (see @file{include/aout/stab.def}). |
e505224d PB |
3475 | |
3476 | The second line describes the language constructs the symbol type | |
3477 | represents. | |
3478 | ||
3479 | The third line is the stab format with the significant stab fields | |
3480 | named and the rest NIL. | |
3481 | ||
3482 | Subsequent lines expand upon the meaning and possible values for each | |
685a5e86 | 3483 | significant stab field. @samp{#} stands in for the type descriptor. |
e505224d PB |
3484 | |
3485 | Finally, any further information. | |
3486 | ||
899bafeb | 3487 | @menu |
8eb5e289 DZ |
3488 | * N_PC:: Pascal global symbol |
3489 | * N_NSYMS:: Number of symbols | |
3490 | * N_NOMAP:: No DST map | |
8eb5e289 DZ |
3491 | * N_M2C:: Modula-2 compilation unit |
3492 | * N_BROWS:: Path to .cb file for Sun source code browser | |
3493 | * N_DEFD:: GNU Modula2 definition module dependency | |
3494 | * N_EHDECL:: GNU C++ exception variable | |
3495 | * N_MOD2:: Modula2 information "for imc" | |
3496 | * N_CATCH:: GNU C++ "catch" clause | |
3497 | * N_SSYM:: Structure or union element | |
8eb5e289 DZ |
3498 | * N_ENTRY:: Alternate entry point |
3499 | * N_SCOPE:: Modula2 scope information (Sun only) | |
3500 | * Gould:: non-base register symbols used on Gould systems | |
3501 | * N_LENG:: Length of preceding entry | |
899bafeb RP |
3502 | @end menu |
3503 | ||
899bafeb | 3504 | @node N_PC |
685a5e86 | 3505 | @section N_PC |
e505224d | 3506 | |
685a5e86 DM |
3507 | @deffn @code{.stabs} N_PC |
3508 | @findex N_PC | |
3509 | Global symbol (for Pascal). | |
e505224d | 3510 | |
899bafeb | 3511 | @example |
e505224d PB |
3512 | "name" -> "symbol_name" <<?>> |
3513 | value -> supposedly the line number (stab.def is skeptical) | |
899bafeb | 3514 | @end example |
e505224d | 3515 | |
899bafeb | 3516 | @display |
f958d5cd | 3517 | @file{stabdump.c} says: |
e505224d | 3518 | |
6fe91f2c | 3519 | global pascal symbol: name,,0,subtype,line |
e505224d | 3520 | << subtype? >> |
899bafeb | 3521 | @end display |
685a5e86 | 3522 | @end deffn |
e505224d | 3523 | |
899bafeb | 3524 | @node N_NSYMS |
685a5e86 DM |
3525 | @section N_NSYMS |
3526 | ||
3527 | @deffn @code{.stabn} N_NSYMS | |
3528 | @findex N_NSYMS | |
3529 | Number of symbols (according to Ultrix V4.0). | |
e505224d | 3530 | |
899bafeb | 3531 | @display |
139741da | 3532 | 0, files,,funcs,lines (stab.def) |
899bafeb | 3533 | @end display |
685a5e86 | 3534 | @end deffn |
e505224d | 3535 | |
899bafeb | 3536 | @node N_NOMAP |
685a5e86 DM |
3537 | @section N_NOMAP |
3538 | ||
3539 | @deffn @code{.stabs} N_NOMAP | |
3540 | @findex N_NOMAP | |
935d305d JK |
3541 | No DST map for symbol (according to Ultrix V4.0). I think this means a |
3542 | variable has been optimized out. | |
e505224d | 3543 | |
899bafeb | 3544 | @display |
139741da | 3545 | name, ,0,type,ignored (stab.def) |
899bafeb | 3546 | @end display |
685a5e86 | 3547 | @end deffn |
e505224d | 3548 | |
899bafeb | 3549 | @node N_M2C |
685a5e86 | 3550 | @section N_M2C |
e505224d | 3551 | |
685a5e86 DM |
3552 | @deffn @code{.stabs} N_M2C |
3553 | @findex N_M2C | |
3554 | Modula-2 compilation unit. | |
e505224d | 3555 | |
899bafeb | 3556 | @example |
685a5e86 | 3557 | "string" -> "unit_name,unit_time_stamp[,code_time_stamp]" |
e505224d PB |
3558 | desc -> unit_number |
3559 | value -> 0 (main unit) | |
139741da | 3560 | 1 (any other unit) |
899bafeb | 3561 | @end example |
b857d956 JK |
3562 | |
3563 | See @cite{Dbx and Dbxtool Interfaces}, 2nd edition, by Sun, 1988, for | |
3564 | more information. | |
3565 | ||
685a5e86 | 3566 | @end deffn |
e505224d | 3567 | |
899bafeb | 3568 | @node N_BROWS |
685a5e86 DM |
3569 | @section N_BROWS |
3570 | ||
3571 | @deffn @code{.stabs} N_BROWS | |
3572 | @findex N_BROWS | |
6fe91f2c | 3573 | Sun source code browser, path to @file{.cb} file |
e505224d | 3574 | |
6fe91f2c | 3575 | <<?>> |
685a5e86 | 3576 | "path to associated @file{.cb} file" |
e505224d | 3577 | |
0a95c18c | 3578 | Note: N_BROWS has the same value as N_BSLINE. |
685a5e86 | 3579 | @end deffn |
e505224d | 3580 | |
899bafeb | 3581 | @node N_DEFD |
685a5e86 DM |
3582 | @section N_DEFD |
3583 | ||
3584 | @deffn @code{.stabn} N_DEFD | |
3585 | @findex N_DEFD | |
3586 | GNU Modula2 definition module dependency. | |
e505224d | 3587 | |
0a95c18c JK |
3588 | GNU Modula-2 definition module dependency. The value is the |
3589 | modification time of the definition file. The other field is non-zero | |
3590 | if it is imported with the GNU M2 keyword @code{%INITIALIZE}. Perhaps | |
3591 | @code{N_M2C} can be used if there are enough empty fields? | |
685a5e86 | 3592 | @end deffn |
e505224d | 3593 | |
899bafeb | 3594 | @node N_EHDECL |
685a5e86 | 3595 | @section N_EHDECL |
e505224d | 3596 | |
685a5e86 DM |
3597 | @deffn @code{.stabs} N_EHDECL |
3598 | @findex N_EHDECL | |
3599 | GNU C++ exception variable <<?>>. | |
e505224d | 3600 | |
685a5e86 DM |
3601 | "@var{string} is variable name" |
3602 | ||
3603 | Note: conflicts with @code{N_MOD2}. | |
3604 | @end deffn | |
e505224d | 3605 | |
899bafeb | 3606 | @node N_MOD2 |
685a5e86 DM |
3607 | @section N_MOD2 |
3608 | ||
3609 | @deffn @code{.stab?} N_MOD2 | |
3610 | @findex N_MOD2 | |
899bafeb | 3611 | Modula2 info "for imc" (according to Ultrix V4.0) |
e505224d | 3612 | |
685a5e86 DM |
3613 | Note: conflicts with @code{N_EHDECL} <<?>> |
3614 | @end deffn | |
e505224d | 3615 | |
899bafeb | 3616 | @node N_CATCH |
685a5e86 DM |
3617 | @section N_CATCH |
3618 | ||
3619 | @deffn @code{.stabn} N_CATCH | |
3620 | @findex N_CATCH | |
6fe91f2c | 3621 | GNU C++ @code{catch} clause |
e505224d | 3622 | |
0a95c18c | 3623 | GNU C++ @code{catch} clause. The value is its address. The desc field |
685a5e86 DM |
3624 | is nonzero if this entry is immediately followed by a @code{CAUGHT} stab |
3625 | saying what exception was caught. Multiple @code{CAUGHT} stabs means | |
0a95c18c JK |
3626 | that multiple exceptions can be caught here. If desc is 0, it means all |
3627 | exceptions are caught here. | |
685a5e86 | 3628 | @end deffn |
e505224d | 3629 | |
899bafeb | 3630 | @node N_SSYM |
685a5e86 DM |
3631 | @section N_SSYM |
3632 | ||
3633 | @deffn @code{.stabn} N_SSYM | |
3634 | @findex N_SSYM | |
3635 | Structure or union element. | |
e505224d | 3636 | |
0a95c18c | 3637 | The value is the offset in the structure. |
899bafeb RP |
3638 | |
3639 | <<?looking at structs and unions in C I didn't see these>> | |
685a5e86 | 3640 | @end deffn |
e505224d | 3641 | |
899bafeb | 3642 | @node N_ENTRY |
685a5e86 | 3643 | @section N_ENTRY |
e505224d | 3644 | |
685a5e86 DM |
3645 | @deffn @code{.stabn} N_ENTRY |
3646 | @findex N_ENTRY | |
6fe91f2c | 3647 | Alternate entry point. |
0a95c18c | 3648 | The value is its address. |
e505224d | 3649 | <<?>> |
685a5e86 | 3650 | @end deffn |
e505224d | 3651 | |
899bafeb | 3652 | @node N_SCOPE |
685a5e86 | 3653 | @section N_SCOPE |
e505224d | 3654 | |
685a5e86 DM |
3655 | @deffn @code{.stab?} N_SCOPE |
3656 | @findex N_SCOPE | |
e505224d PB |
3657 | Modula2 scope information (Sun linker) |
3658 | <<?>> | |
685a5e86 | 3659 | @end deffn |
e505224d | 3660 | |
899bafeb RP |
3661 | @node Gould |
3662 | @section Non-base registers on Gould systems | |
ded6bcab | 3663 | |
685a5e86 DM |
3664 | @deffn @code{.stab?} N_NBTEXT |
3665 | @deffnx @code{.stab?} N_NBDATA | |
3666 | @deffnx @code{.stab?} N_NBBSS | |
3667 | @deffnx @code{.stab?} N_NBSTS | |
3668 | @deffnx @code{.stab?} N_NBLCS | |
3669 | @findex N_NBTEXT | |
3670 | @findex N_NBDATA | |
3671 | @findex N_NBBSS | |
3672 | @findex N_NBSTS | |
3673 | @findex N_NBLCS | |
ded6bcab JK |
3674 | These are used on Gould systems for non-base registers syms. |
3675 | ||
3676 | However, the following values are not the values used by Gould; they are | |
3677 | the values which GNU has been documenting for these values for a long | |
3678 | time, without actually checking what Gould uses. I include these values | |
3679 | only because perhaps some someone actually did something with the GNU | |
3680 | information (I hope not, why GNU knowingly assigned wrong values to | |
3681 | these in the header file is a complete mystery to me). | |
e505224d | 3682 | |
899bafeb | 3683 | @example |
139741da RP |
3684 | 240 0xf0 N_NBTEXT ?? |
3685 | 242 0xf2 N_NBDATA ?? | |
3686 | 244 0xf4 N_NBBSS ?? | |
3687 | 246 0xf6 N_NBSTS ?? | |
3688 | 248 0xf8 N_NBLCS ?? | |
899bafeb | 3689 | @end example |
685a5e86 | 3690 | @end deffn |
e505224d | 3691 | |
899bafeb | 3692 | @node N_LENG |
685a5e86 | 3693 | @section N_LENG |
e505224d | 3694 | |
685a5e86 DM |
3695 | @deffn @code{.stabn} N_LENG |
3696 | @findex N_LENG | |
e505224d | 3697 | Second symbol entry containing a length-value for the preceding entry. |
0a95c18c | 3698 | The value is the length. |
685a5e86 | 3699 | @end deffn |
e505224d | 3700 | |
899bafeb | 3701 | @node Questions |
bf9d2537 | 3702 | @appendix Questions and Anomalies |
e505224d PB |
3703 | |
3704 | @itemize @bullet | |
3705 | @item | |
dd8126d9 | 3706 | @c I think this is changed in GCC 2.4.5 to put the line number there. |
6fe91f2c | 3707 | For GNU C stabs defining local and global variables (@code{N_LSYM} and |
0a95c18c JK |
3708 | @code{N_GSYM}), the desc field is supposed to contain the source |
3709 | line number on which the variable is defined. In reality the desc | |
dd8126d9 | 3710 | field is always 0. (This behavior is defined in @file{dbxout.c} and |
0a95c18c | 3711 | putting a line number in desc is controlled by @samp{#ifdef |
dd8126d9 JK |
3712 | WINNING_GDB}, which defaults to false). GDB supposedly uses this |
3713 | information if you say @samp{list @var{var}}. In reality, @var{var} can | |
3714 | be a variable defined in the program and GDB says @samp{function | |
6fe91f2c | 3715 | @var{var} not defined}. |
e505224d PB |
3716 | |
3717 | @item | |
6fe91f2c DM |
3718 | In GNU C stabs, there seems to be no way to differentiate tag types: |
3719 | structures, unions, and enums (symbol descriptor @samp{T}) and typedefs | |
3720 | (symbol descriptor @samp{t}) defined at file scope from types defined locally | |
3721 | to a procedure or other more local scope. They all use the @code{N_LSYM} | |
e505224d | 3722 | stab type. Types defined at procedure scope are emited after the |
6fe91f2c | 3723 | @code{N_RBRAC} of the preceding function and before the code of the |
e505224d PB |
3724 | procedure in which they are defined. This is exactly the same as |
3725 | types defined in the source file between the two procedure bodies. | |
4d7f562d | 3726 | GDB overcompensates by placing all types in block #1, the block for |
6fe91f2c DM |
3727 | symbols of file scope. This is true for default, @samp{-ansi} and |
3728 | @samp{-traditional} compiler options. (Bugs gcc/1063, gdb/1066.) | |
e505224d PB |
3729 | |
3730 | @item | |
6fe91f2c DM |
3731 | What ends the procedure scope? Is it the proc block's @code{N_RBRAC} or the |
3732 | next @code{N_FUN}? (I believe its the first.) | |
e505224d PB |
3733 | |
3734 | @item | |
24dcc707 | 3735 | @c FIXME: This should go with the other stuff about global variables. |
e505224d PB |
3736 | Global variable stabs don't have location information. This comes |
3737 | from the external symbol for the same variable. The external symbol | |
3738 | has a leading underbar on the _name of the variable and the stab does | |
3739 | not. How do we know these two symbol table entries are talking about | |
24dcc707 JK |
3740 | the same symbol when their names are different? (Answer: the debugger |
3741 | knows that external symbols have leading underbars). | |
e505224d | 3742 | |
24dcc707 JK |
3743 | @c FIXME: This is absurdly vague; there all kinds of differences, some |
3744 | @c of which are the same between gnu & sun, and some of which aren't. | |
dd8126d9 JK |
3745 | @c In particular, I'm pretty sure GCC works with Sun dbx by default. |
3746 | @c @item | |
3747 | @c Can GCC be configured to output stabs the way the Sun compiler | |
3748 | @c does, so that their native debugging tools work? <NO?> It doesn't by | |
3749 | @c default. GDB reads either format of stab. (GCC or SunC). How about | |
3750 | @c dbx? | |
e505224d PB |
3751 | @end itemize |
3752 | ||
bf9d2537 DM |
3753 | @node XCOFF Differences |
3754 | @appendix Differences Between GNU Stabs in a.out and GNU Stabs in XCOFF | |
e505224d | 3755 | |
497e44a5 | 3756 | @c FIXME: Merge *all* these into the main body of the document. |
f958d5cd | 3757 | The AIX/RS6000 native object file format is XCOFF with stabs. This |
497e44a5 JK |
3758 | appendix only covers those differences which are not covered in the main |
3759 | body of this document. | |
e505224d PB |
3760 | |
3761 | @itemize @bullet | |
e505224d | 3762 | @item |
dd8126d9 JK |
3763 | BSD a.out stab types correspond to AIX XCOFF storage classes. In general |
3764 | the mapping is @code{N_@var{stabtype}} becomes @code{C_@var{stabtype}}. | |
3765 | Some stab types in a.out are not supported in XCOFF; most of these use | |
3766 | @code{C_DECL}. | |
e505224d | 3767 | |
24dcc707 JK |
3768 | @c FIXME: I think they are trying to say something about whether the |
3769 | @c assembler defaults the value to the location counter. | |
e505224d | 3770 | @item |
685a5e86 | 3771 | If the XCOFF stab is an @code{N_FUN} (@code{C_FUN}) then follow the |
dd8126d9 | 3772 | string field with @samp{,.} instead of just @samp{,}. |
e505224d PB |
3773 | @end itemize |
3774 | ||
6fe91f2c | 3775 | I think that's it for @file{.s} file differences. They could stand to be |
e505224d | 3776 | better presented. This is just a list of what I have noticed so far. |
6fe91f2c DM |
3777 | There are a @emph{lot} of differences in the information in the symbol |
3778 | tables of the executable and object files. | |
e505224d | 3779 | |
f958d5cd | 3780 | Mapping of a.out stab types to XCOFF storage classes: |
e505224d PB |
3781 | |
3782 | @example | |
139741da | 3783 | stab type storage class |
e505224d | 3784 | ------------------------------- |
139741da | 3785 | N_GSYM C_GSYM |
43603088 | 3786 | N_FNAME unused |
139741da RP |
3787 | N_FUN C_FUN |
3788 | N_STSYM C_STSYM | |
3789 | N_LCSYM C_STSYM | |
43603088 | 3790 | N_MAIN unknown |
139741da RP |
3791 | N_PC unknown |
3792 | N_RSYM C_RSYM | |
dd8126d9 | 3793 | unknown C_RPSYM |
139741da RP |
3794 | N_M2C unknown |
3795 | N_SLINE unknown | |
3796 | N_DSLINE unknown | |
3797 | N_BSLINE unknown | |
3798 | N_BROWSE unchanged | |
3799 | N_CATCH unknown | |
3800 | N_SSYM unknown | |
3801 | N_SO unknown | |
3802 | N_LSYM C_LSYM | |
dd8126d9 | 3803 | various C_DECL |
139741da RP |
3804 | N_BINCL unknown |
3805 | N_SOL unknown | |
3806 | N_PSYM C_PSYM | |
3807 | N_EINCL unknown | |
3808 | N_ENTRY C_ENTRY | |
3809 | N_LBRAC unknown | |
3810 | N_EXCL unknown | |
3811 | N_SCOPE unknown | |
3812 | N_RBRAC unknown | |
3813 | N_BCOMM C_BCOMM | |
3814 | N_ECOMM C_ECOMM | |
3815 | N_ECOML C_ECOML | |
3816 | ||
3817 | N_LENG unknown | |
e505224d PB |
3818 | @end example |
3819 | ||
bf9d2537 DM |
3820 | @node Sun Differences |
3821 | @appendix Differences Between GNU Stabs and Sun Native Stabs | |
e505224d | 3822 | |
497e44a5 JK |
3823 | @c FIXME: Merge all this stuff into the main body of the document. |
3824 | ||
e505224d PB |
3825 | @itemize @bullet |
3826 | @item | |
6fe91f2c DM |
3827 | GNU C stabs define @emph{all} types, file or procedure scope, as |
3828 | @code{N_LSYM}. Sun doc talks about using @code{N_GSYM} too. | |
e505224d | 3829 | |
e505224d | 3830 | @item |
4e9570e8 JK |
3831 | Sun C stabs use type number pairs in the format |
3832 | (@var{file-number},@var{type-number}) where @var{file-number} is a | |
3833 | number starting with 1 and incremented for each sub-source file in the | |
3834 | compilation. @var{type-number} is a number starting with 1 and | |
6fe91f2c DM |
3835 | incremented for each new type defined in the compilation. GNU C stabs |
3836 | use the type number alone, with no source file number. | |
e505224d PB |
3837 | @end itemize |
3838 | ||
bf9d2537 DM |
3839 | @node Stabs In ELF |
3840 | @appendix Using Stabs With The ELF Object File Format | |
935d305d | 3841 | |
6fe91f2c DM |
3842 | The ELF object file format allows tools to create object files with |
3843 | custom sections containing any arbitrary data. To use stabs in ELF | |
935d305d JK |
3844 | object files, the tools create two custom sections, a section named |
3845 | @code{.stab} which contains an array of fixed length structures, one | |
3846 | struct per stab, and a section named @code{.stabstr} containing all the | |
3847 | variable length strings that are referenced by stabs in the @code{.stab} | |
3848 | section. The byte order of the stabs binary data matches the byte order | |
6fe91f2c DM |
3849 | of the ELF file itself, as determined from the @code{EI_DATA} field in |
3850 | the @code{e_ident} member of the ELF header. | |
935d305d | 3851 | |
4e9570e8 | 3852 | The first stab in the @code{.stab} section for each compilation unit is |
935d305d JK |
3853 | synthetic, generated entirely by the assembler, with no corresponding |
3854 | @code{.stab} directive as input to the assembler. This stab contains | |
3855 | the following fields: | |
cc4fb848 | 3856 | |
935d305d JK |
3857 | @table @code |
3858 | @item n_strx | |
3859 | Offset in the @code{.stabstr} section to the source filename. | |
cc4fb848 | 3860 | |
935d305d JK |
3861 | @item n_type |
3862 | @code{N_UNDF}. | |
cc4fb848 | 3863 | |
935d305d | 3864 | @item n_other |
cc4fb848 FF |
3865 | Unused field, always zero. |
3866 | ||
935d305d | 3867 | @item n_desc |
6fe91f2c | 3868 | Count of upcoming symbols, i.e., the number of remaining stabs for this |
935d305d | 3869 | source file. |
cc4fb848 | 3870 | |
935d305d JK |
3871 | @item n_value |
3872 | Size of the string table fragment associated with this source file, in | |
cc4fb848 | 3873 | bytes. |
935d305d | 3874 | @end table |
cc4fb848 | 3875 | |
935d305d | 3876 | The @code{.stabstr} section always starts with a null byte (so that string |
cc4fb848 FF |
3877 | offsets of zero reference a null string), followed by random length strings, |
3878 | each of which is null byte terminated. | |
3879 | ||
6fe91f2c | 3880 | The ELF section header for the @code{.stab} section has its |
935d305d | 3881 | @code{sh_link} member set to the section number of the @code{.stabstr} |
6fe91f2c | 3882 | section, and the @code{.stabstr} section has its ELF section |
935d305d JK |
3883 | header @code{sh_type} member set to @code{SHT_STRTAB} to mark it as a |
3884 | string table. | |
3885 | ||
577379ab JK |
3886 | To keep linking fast, you don't want the linker to have to relocate very |
3887 | many stabs. Thus Sun has invented a scheme in which addresses in the | |
3888 | @code{n_value} field are relative to the source file (or some entity | |
3889 | smaller than a source file, like a function). To find the address of | |
3890 | each section corresponding to a given source file, the compiler puts out | |
31a932d8 | 3891 | symbols giving the address of each section for a given source file. |
f8cbe518 JK |
3892 | Since these are ELF (not stab) symbols, the linker relocates them |
3893 | correctly without having to touch the stabs section. They are named | |
3894 | @code{Bbss.bss} for the bss section, @code{Ddata.data} for the data | |
3895 | section, and @code{Drodata.rodata} for the rodata section. For the text | |
3896 | section, there is no such symbol (but there should be, see below). For | |
b563c370 | 3897 | an example of how these symbols work, @xref{ELF and SOM Transformations}. GCC |
31a932d8 | 3898 | does not provide these symbols; it instead relies on the stabs getting |
577379ab JK |
3899 | relocated. Thus addresses which would normally be relative to |
3900 | @code{Bbss.bss}, etc., are already relocated. The Sun linker provided | |
3901 | with Solaris 2.2 and earlier relocates stabs using normal ELF relocation | |
3902 | information, as it would do for any section. Sun has been threatening | |
3903 | to kludge their linker to not do this (to speed up linking), even though | |
3904 | the correct way to avoid having the linker do these relocations is to | |
3905 | have the compiler no longer output relocatable values. Last I heard | |
3906 | they had been talked out of the linker kludge. See Sun point patch | |
3907 | 101052-01 and Sun bug 1142109. With the Sun compiler this affects | |
f8cbe518 JK |
3908 | @samp{S} symbol descriptor stabs (@pxref{Statics}) and functions |
3909 | (@pxref{Procedures}). In the latter case, to adopt the clean solution | |
3910 | (making the value of the stab relative to the start of the compilation | |
3911 | unit), it would be necessary to invent a @code{Ttext.text} symbol, | |
3912 | analogous to the @code{Bbss.bss}, etc., symbols. I recommend this | |
3913 | rather than using a zero value and getting the address from the ELF | |
3914 | symbols. | |
cc4fb848 | 3915 | |
577379ab JK |
3916 | Finding the correct @code{Bbss.bss}, etc., symbol is difficult, because |
3917 | the linker simply concatenates the @code{.stab} sections from each | |
3918 | @file{.o} file without including any information about which part of a | |
3919 | @code{.stab} section comes from which @file{.o} file. The way GDB does | |
3920 | this is to look for an ELF @code{STT_FILE} symbol which has the same | |
3921 | name as the last component of the file name from the @code{N_SO} symbol | |
3922 | in the stabs (for example, if the file name is @file{../../gdb/main.c}, | |
3923 | it looks for an ELF @code{STT_FILE} symbol named @code{main.c}). This | |
3924 | loses if different files have the same name (they could be in different | |
3925 | directories, a library could have been copied from one system to | |
3926 | another, etc.). It would be much cleaner to have the @code{Bbss.bss} | |
3927 | symbols in the stabs themselves. Having the linker relocate them there | |
3928 | is no more work than having the linker relocate ELF symbols, and it | |
3929 | solves the problem of having to associate the ELF and stab symbols. | |
3930 | However, no one has yet designed or implemented such a scheme. | |
3931 | ||
685a5e86 DM |
3932 | @node Symbol Types Index |
3933 | @unnumbered Symbol Types Index | |
3934 | ||
3935 | @printindex fn | |
3936 | ||
e505224d PB |
3937 | @contents |
3938 | @bye |