Re: RFC: fix PR mi/10693

[Tom Tromey <tromey@redhat.com>]

Tom> So I think we should instead just document that symbols-loaded is
Tom> emitted for compatibility but is not actually useful.

Like this.

Ok?

Tom

2011-02-04  Tom Tromey  <tromey@redhat.com>

	* gdb.texinfo (GDB/MI Async Records): Document that symbols-loaded
	is not useful.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 5dc0af0..5ec7c1a 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -24771,11 +24771,12 @@ opaque identifier of the library.  For remote debugging case,
 @var{target-name} and @var{host-name} fields give the name of the
 library file on the target, and on the host respectively.  For native
 debugging, both those fields have the same value.  The
-@var{symbols-loaded} field reports if the debug symbols for this
-library are loaded.  The @var{thread-group} field, if present,
-specifies the id of the thread group in whose context the library was loaded.
-If the field is absent, it means the library was loaded in the context
-of all present thread groups.
+@var{symbols-loaded} field is emitted only for backward compatibility
+and should not be relied on to convey any useful information.  The
+@var{thread-group} field, if present, specifies the id of the thread
+group in whose context the library was loaded.  If the field is
+absent, it means the library was loaded in the context of all present
+thread groups.
 
 @item =library-unloaded,...
 Reports that a library was unloaded by the program.  This notification