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