[Bug 638] New - Document Wine debugging channels

http://bugs.codeweavers.com/show_bug.cgi?id=638

*** shadow/638	Thu May  2 14:29:26 2002
--- shadow/638.tmp.10913	Thu May  2 14:29:26 2002
***************
*** 0 ****
--- 1,36 ----
+ +============================================================================+
+ | Document Wine debugging channels                                           |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 638                         Product: Wine                    |
+ |       Status: UNCONFIRMED                 Version: unspecified             |
+ |   Resolution:                            Platform:                         |
+ |     Severity: normal                   OS/Version: All                     |
+ |     Priority: P1                        Component: wine-documentation      |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: [e-mail]                                         |
+ |  Reported By: [e-mail]                                              |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |    Milestone: TargetMilestone: ---                                         |
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ Write description of the debugging channels to documentation/running.sgml.
+ This is pretty easy to do - search the .c files for macros
+ WINE_DEFAULT_DEBUG_CHANNEL and WINE_DECLARE_DEBUG_CHANNEL. Some files declare
+ a few channels. E.g. file loader/module.c has following declarations:
+ 
+ WINE_DEFAULT_DEBUG_CHANNEL(module);
+ WINE_DECLARE_DEBUG_CHANNEL(win32);
+ WINE_DECLARE_DEBUG_CHANNEL(loaddll);
+ 
+ Knowing modules where the channels used and looking how these channels
+ used in the modules you can get an idea what kind of debugging information
+ these channels propagate.
+ Some information from documentation/configuring.sgml can help you. As usual
+ google and msdn.microsoft.com are also your best friends in this (well, probably
+ not the latter ;-).
+ 
+ Please, update list of channels if you find a new one. Note, besides file 
+ documentation/running.sgml the debugging channels are listed in
+ documentation/wine.man.in.
\ No newline at end of file