[3/3] winedbg: Make limitations of set command clearer in man page.

[Dylan Smith]

The way debugging is done in wine currently prevents debug channels to
be set if they weren't specified in WINEDEBUG.  This is because the
debug flags appear to be cached for unspecified channels within static
structures for each object file the first time the flags are retrieved
(e.g. when reaching a TRACE statement).  Fixing this behaviour to make
it more flexible would have a likely unacceptable performance impact, so
instead this limitation should be noted in winedbg's man page.
---
 programs/winedbg/winedbg.man.in |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)
-------------- next part --------------
diff --git a/programs/winedbg/winedbg.man.in b/programs/winedbg/winedbg.man.in
index 34003d9..fb91d6b 100644
--- a/programs/winedbg/winedbg.man.in
+++ b/programs/winedbg/winedbg.man.in
@@ -369,8 +369,9 @@ Lists all w-threads in Wine session
 .IP \fBinfo\ exception\fR
 Lists the exception frames (starting from current stack frame)
 .PP
-It is possible to turn on and off Wine's debug messages as you are
-debugging using the \fBset\fR command. 
+Debug messages can be turned on and off as you are debugging using
+the \fBset\fR command, but only for channels initialized with the
+\fIWINEDEBUG\fR environment variable.
 .IP \fBset\ warn\ +\ win\fR
 Turns on warn on \fB'win'\fR channel
 .IP \fBset\ +\ win\fR