darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Catch up to changes recorded in GDB ChangeLog, to wit:

Browse source 
1) "show copying" and "show warranty" in sample output (instead of obs. "info")
2) new command "printpsyms"
3) Complaint "const/volatile indicator missing" re-enabled
4) Complaint "C++ type mismatch..." now "info mismatch..."
This commit is contained in:
Roland Pesch 1991-10-14 20:36:50 +00:00
parent c7aab257f9
commit 440d983441
1 changed files with 28 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

50
gdb/doc/gdb.texinfo
View file

@ -31,7 +31,7 @@ _include__(gdbVN.m4)
@c @c
@syncodeindex ky cp @syncodeindex ky cp
@c FOR UPDATES LEADING TO THIS DRAFT, GDB CHANGELOG CONSULTED BETWEEN: @c FOR UPDATES LEADING TO THIS DRAFT, GDB CHANGELOG CONSULTED BETWEEN:
@c Fri Sep 20 16:10:52 1991 John Gilmore (gnu at cygnus.com) @c Fri Oct 11 23:27:06 1991 John Gilmore (gnu at cygnus.com)
@c Sat Dec 22 02:51:40 1990 John Gilmore (gnu at cygint) @c Sat Dec 22 02:51:40 1990 John Gilmore (gnu at cygint)
@ifinfo @ifinfo
This file documents the GNU debugger _GDBN__. This file documents the GNU debugger _GDBN__.
@ -412,10 +412,10 @@ omitted from this list, we would like to add your names!
So that they may not regard their long labor as thankless, we So that they may not regard their long labor as thankless, we
particularly thank those who shepherded GDB through major releases: John particularly thank those who shepherded GDB through major releases: John
Gilmore (releases _GDB_VN__, 4.0); Jim Kingdon (releases 3.9, 3.5, 3.4, 3.3); Gilmore (releases _GDB_VN__, 4.1, 4.0); Jim Kingdon (releases 3.9, 3.5,
and Randy Smith (releases 3.2, 3.1, 3.0). As major maintainer of GDB 3.4, 3.3); and Randy Smith (releases 3.2, 3.1, 3.0). As major
for some period, each contributed significantly to the structure, maintainer of GDB for some period, each contributed significantly to the
stability, and capabilities of the entire debugger. structure, stability, and capabilities of the entire debugger.
Richard Stallman, assisted at various times by Pete TerMaat, Chris Richard Stallman, assisted at various times by Pete TerMaat, Chris
Hanson, and Richard Mlynarik, handled releases through 2.8. Hanson, and Richard Mlynarik, handled releases through 2.8.
@ -600,8 +600,8 @@ Let's use _GDBN__ to try to see what's going on.
@smallexample @smallexample
$ @i{_GDBP__ m4} $ @i{_GDBP__ m4}
GDB is free software and you are welcome to distribute copies of it GDB is free software and you are welcome to distribute copies of it
under certain conditions; type "info copying" to see the conditions. under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "info warranty" for details. There is absolutely no warranty for GDB; type "show warranty" for details.
GDB _GDB_VN__, Copyright 1991 Free Software Foundation, Inc... GDB _GDB_VN__, Copyright 1991 Free Software Foundation, Inc...
(_GDBP__) (_GDBP__)
@end smallexample @end smallexample
@ -5314,14 +5314,23 @@ which match the regular-expression @var{regexp}.
@end ignore @end ignore
@item printsyms @var{filename} @item printsyms @var{filename}
@itemx printpsyms @var{filename}
@kindex printsyms @kindex printsyms
Write a dump of debugging symbol data into the file @cindex symbol dump
@var{filename}. Only symbols with debugging data are included. _GDBN__ @kindex printsyms
includes all the symbols it already knows about: that is, @var{filename} @cindex partial symbol dump
reflects symbols for only those files whose symbols _GDBN__ has read. Write a dump of debugging symbol data into the file @var{filename}.
You can find out which files these are using the command @code{info Only symbols with debugging data are included. If you use
files}. The description of @code{symbol-file} describes how _GDBN__ @code{printsyms}, _GDBN__ includes all the symbols for which it has
reads symbols; both commands are described under @ref{Files}. already collected full details: that is, @var{filename} reflects symbols
for only those files whose symbols _GDBN__ has read. You can find out
which files these are using the command @code{info files}. On the other
hand, if you use @code{printpsyms}, the dump also shows information
about symbols that _GDBN__ only knows partially---that is, symbols
defined in files that _GDBN__ has not yet read. The description of
@code{symbol-file} describes how _GDBN__ reads symbols; both commands
are described under @ref{Files}.
@end table @end table
@node Altering, _GDBN__ Files, Symbols, Top @node Altering, _GDBN__ Files, Symbols, Top
@ -5834,18 +5843,15 @@ examine @code{*bufp} to see the symbol.
@item stub type has NULL name @item stub type has NULL name
_GDBN__ could not find the full definition for a struct or class. _GDBN__ could not find the full definition for a struct or class.
@ignore @item const/volatile indicator missing (ok if using g++ v1.x), got@dots{}
@c this is #if 0'd in dbxread.c as of (at least!) 17 may 1991
@item const/volatile indicator missing, got '@var{X}'
The symbol information for a C++ member function is missing some The symbol information for a C++ member function is missing some
information that the compiler should have output for it. information that recent versions of the compiler should have output
@end ignore for it.
@item C++ type mismatch between compiler and debugger @item info mismatch between compiler and debugger
_GDBN__ could not parse a type specification output by the compiler _GDBN__ could not parse a type specification output by the compiler.
for some C++ object.
@end table @end table