espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-06-20 18:08:24 +08:00
Code Issues Packages Projects Releases Wiki Activity

fixes re arrays and continuations

Browse Source
This commit is contained in:
Jim Kingdon
1993-03-19 18:48:45 +00:00
parent 9729ef2206
commit b6963343f6
2 changed files with 16 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
gdb/doc/ChangeLog
View File

@ -1,5 +1,7 @@
Fri Mar 19 10:23:34 1993 Jim Kingdon (kingdon@cygnus.com) Fri Mar 19 10:23:34 1993 Jim Kingdon (kingdon@cygnus.com)
* stabs.texinfo: Fixes re arrays and continuations.
* gdbint.texinfo: Add XCOFF node. * gdbint.texinfo: Add XCOFF node.
Mon Mar 8 15:52:18 1993 John Gilmore (gnu@cygnus.com) Mon Mar 8 15:52:18 1993 John Gilmore (gnu@cygnus.com)

24
gdb/doc/stabs.texinfo
View File

@ -208,16 +208,17 @@ This is described more thoroughly in the section on types. @xref{Type
Descriptors,,Table D: Type Descriptors}, for a list of Descriptors,,Table D: Type Descriptors}, for a list of
@var{type_descriptor} values. @var{type_descriptor} values.
@c FIXME! "too long" below introduced at J Gilmore's request; used to All this can make the @code{"@var{string}"} field quite long. All
@c say "more than 80 chars". Why is vaguer better? versions of GDB, and some versions of DBX, can handle arbitrarily long
All this can make the @code{"@var{string}"} field quite long. When the strings. But many versions of DBX cretinously limit the strings to
@code{"@var{string}"} part of a stab is too long, the compiler splits about 80 characters, so compilers which must work with such DBX's need
the @code{.stabs} directive into two @code{.stabs} directives. Both to split the @code{.stabs} directive into several @code{.stabs}
stabs duplicate exactly all but the @code{"@var{string}"} field. The directives. Each stab duplicates exactly all but the
@code{"@var{string}"} field of the first stab contains the first part of @code{"@var{string}"} field. The @code{"@var{string}"} field of the
the overlong string, marked as continued with a double-backslash at the every stab except the last is marked as continued with a
end. The @code{"@var{string}"} field of the second stab holds the double-backslash at the end. Removing the backslashes and concatenating
second half of the overlong string. the @code{"@var{string}"} fields of each stab produces the original,
long string.
@node C example @node C example
@section A simple example in C source @section A simple example in C source
@ -3127,6 +3128,9 @@ GNU C stabs define *all* types, file or procedure scope, as
N_LSYM. Sun doc talks about using N_GSYM too. N_LSYM. Sun doc talks about using N_GSYM too.
@item @item
@c FIXME: are you sure? The 'a' is usually followed by an 'r' which means
@c "range type" but that doesn't mean the type descriptor is 'ar'.
@c A (non-C) array could be indexed by an enum, for example. -kingdon
GNU C stabs use `ar' as type descriptor when defining arrays vs. just GNU C stabs use `ar' as type descriptor when defining arrays vs. just
`a' in Sun doc. `a' in Sun doc.