diff options
author | Jim Kingdon <jkingdon@engr.sgi.com> | 1994-04-20 18:26:12 +0000 |
---|---|---|
committer | Jim Kingdon <jkingdon@engr.sgi.com> | 1994-04-20 18:26:12 +0000 |
commit | 50cca378931f2623f4df0e1f4b8c61321185efde (patch) | |
tree | 4ad907d56a1c7435f212fdab00761cd9a8b44b43 /gdb/doc/stabs.texinfo | |
parent | b2689e8e79051b6dfe1da0ae5a9ce78a11988f0b (diff) | |
download | gdb-50cca378931f2623f4df0e1f4b8c61321185efde.zip gdb-50cca378931f2623f4df0e1f4b8c61321185efde.tar.gz gdb-50cca378931f2623f4df0e1f4b8c61321185efde.tar.bz2 |
* stabs.texinfo (Stab Section Basics): Say what is in .stab
section, and say n_strx field is compilation unit relative.
* stabs.texinfo: Don't use @code for a.out when it is the name of
an object file format.
Diffstat (limited to 'gdb/doc/stabs.texinfo')
-rw-r--r-- | gdb/doc/stabs.texinfo | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/gdb/doc/stabs.texinfo b/gdb/doc/stabs.texinfo index 20e5035..3d68856 100644 --- a/gdb/doc/stabs.texinfo +++ b/gdb/doc/stabs.texinfo @@ -533,7 +533,7 @@ one has complained). A function is represented by an @samp{F} symbol descriptor for a global (extern) function, and @samp{f} for a static (local) function. The -value is the address of the start of the function. For @code{a.out}, it +value is the address of the start of the function. For a.out, it is already relocated. For stabs in ELF, the SunPRO compiler version 2.0.1 and GCC put out an address which gets relocated by the linker. In a future release SunPRO is planning to put out zero, in which case the @@ -3028,7 +3028,7 @@ description in the class stab shows this ordering. @appendix Table of Stab Types The following are all the possible values for the stab type field, for -@code{a.out} files, in numeric order. This does not apply to XCOFF, but +a.out files, in numeric order. This does not apply to XCOFF, but it does apply to stabs in sections (@pxref{Stab Sections}). Stabs in ECOFF use these values but add 0x8f300 to distinguish them from non-stab symbols. @@ -3916,7 +3916,11 @@ byte order of the stabs binary data depends on the object file format. For ELF, it matches the byte order of the ELF file itself, as determined from the @code{EI_DATA} field in the @code{e_ident} member of the ELF header. For SOM, it is always big-endian (is this true??? FIXME). For -COFF, it matches the byte order of the COFF headers. +COFF, it matches the byte order of the COFF headers. The meaning of the +fields is the same as for a.out (@pxref{Symbol Table Format}), except +that the @code{n_strx} field is relative to the strings for the current +compilation unit (which can be found using the synthetic N_UNDF stab +described below), rather than the entire string table. The first stab in the @code{.stab} section for each compilation unit is synthetic, generated entirely by the assembler, with no corresponding |