* gdb.texinfo: Remove stuff about ar and 14 character filenames.

I believe this was fixed by the 13 Sep 89 change to print_frame_info.
	Also, modern versions of ar like BSD 4.4 or SVR4 don't have this bug.
This commit is contained in:
Jim Kingdon 1993-09-30 17:01:45 +00:00
parent 8f341c15fd
commit 79bda3c7e8
2 changed files with 6 additions and 16 deletions

View File

@ -1,3 +1,9 @@
Thu Sep 30 11:54:38 1993 Jim Kingdon (kingdon@lioth.cygnus.com)
* gdb.texinfo: Remove stuff about ar and 14 character filenames.
I believe this was fixed by the 13 Sep 89 change to print_frame_info.
Also, modern versions of ar like BSD 4.4 or SVR4 don't have this bug.
Wed Sep 22 21:22:11 1993 Jim Kingdon (kingdon@lioth.cygnus.com)
* remote.texi (Bootstrapping): Discuss 386 call gates.

View File

@ -1409,22 +1409,6 @@ Older versions of the GNU C compiler permitted a variant option
@w{@samp{-gg}} for debugging information. @value{GDBN} no longer supports this
format; if your GNU C compiler has this option, do not use it.
@ignore
@comment As far as I know, there are no cases in which @value{GDBN} will
@comment produce strange output in this case. (but no promises).
If your program includes archives made with the @code{ar} program, and
if the object files used as input to @code{ar} were compiled without the
@samp{-g} option and have names longer than 15 characters, @value{GDBN} will get
confused reading your program's symbol table. No error message will be
given, but @value{GDBN} may behave strangely. The reason for this problem is a
deficiency in the Unix archive file format, which cannot represent file
names longer than 15 characters.
To avoid this problem, compile the archive members with the @samp{-g}
option or use shorter file names. Alternatively, use a version of GNU
@code{ar} dated more recently than August 1989.
@end ignore
@need 2000
@node Starting
@section Starting your program