Fixes to auto-solib-add documentation.

[Jim Kingdon <kingdon at redhat dot com>]

The non-HPUX thing should be self-explanatory.

The other one is a response to the problems by which "set
auto-solib-add 0" on Linux with threaded programs can be one source of
spurious SIGTRAP's.  I'd much rather provide a way for GDB to detect
this situation and print a warning or something, but I looked at the
code a bit and it wasn't clear there was a good way to do that.  So
documenting it is better than nothing.

2000-03-10  Jim Kingdon  <kingdon@redhat.com>

	* gdb.texinfo (Files): document "set auto-solib-add" for non-HPUX
	and also mention the thing about setting it to 0 in .gdbinit.

Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.1.1.14
diff -u -r1.1.1.14 gdb.texinfo
--- gdb.texinfo	2000/01/18 00:54:25	1.1.1.14
+++ gdb.texinfo	2000/03/12 00:16:48
@@ -7909,6 +7909,17 @@
 Otherwise, symbols must be loaded manually, using the
 @code{sharedlibrary} command.  The default threshold is 100 megabytes.
 
+On non HP-UX systems which support shared libraries, the auto-solib-add
+setting still exists, but it is simply zero for manual loading and
+nonzero to load libraries automatically.
+
+Note that setting manual loading can sometimes have unexpected
+consequences, since @value{GDBN} itself may be looking for some of the
+symbols to be present to perform its own tasks (including thread
+debugging for example).  One technique which can help is to set
+auto-solib-add to zero only after you have started your program running
+and the basic libraries (such as thread libraries) have been loaded.
+
 @kindex show auto-solib-add
 @item show auto-solib-add
 Display the current autoloading size threshold, in megabytes.