[PATCH] Update documentation for the default value of main set worker-threads

[cbiesinger@chromium.org]

From: Christian Biesinger <cbiesinger@google.com>

I forgot to update this documentation when I changed the default for
maint set worker-threads to be 0. This is a branch-only change, because
on trunk this has been changed back to unlimited.

OK for branch? Let me know if I need to file a bug report for this.

gdb/doc/ChangeLog:

2019-12-14  Christian Biesinger  <cbiesinger@google.com>

	* gdb.texinfo (Maintenance Commands): Update documentation for
	maint set worker-threads to say the default is 0.

Change-Id: I75b74c5da599e657ee94daa8c88b5a097bc58d15
---
 gdb/doc/gdb.texinfo | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 4d25f755d7..a272f634e2 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -38460,10 +38460,10 @@ On capable hosts, @value{GDBN} may use multiple threads to speed up
 certain CPU-intensive operations, such as demangling symbol names.
 While the number of threads used by @value{GDBN} may vary, this
 command can be used to set an upper bound on this number.  The default
-is @code{unlimited}, which lets @value{GDBN} choose a reasonable
-number.  Note that this only controls worker threads started by
-@value{GDBN} itself; libraries used by @value{GDBN} may start threads
-of their own.
+is @code{0} (disabled).  A value of @code{unlimited} lets @value{GDBN} choose a
+reasonable number.  Note that this only controls worker threads started by
+@value{GDBN} itself; libraries used by @value{GDBN} may start threads of their
+own.
 
 @kindex maint set profile
 @kindex maint show profile
-- 
2.24.1.735.g03f4e72817-goog