To better manage the large volume of debugging messages that Wine can generate, we divide the messages on a component basis, and classify them based on the severity of the reported problem. Therefore a message belongs to a channel and a class respectively. This section will describe the debugging classes, how you can create a new debugging channel, what the debugging API is, and how you can control the debugging output. A picture is worth a thousand words, so here are a few examples of the debugging API in action: ERR("lock_count == 0 ... please report\n"); FIXME("Unsupported RTL style!\n"); WARN(": file seems to be truncated!\n"); TRACE("[%p]: new horz extent = %d\n", hwnd, extent ); MESSAGE( "Could not create graphics driver '%s'\n", buffer ); A debugging class categorizes a message based on the severity of the reported problem. There is a fixed set of classes, and you must carefully choose the appropriate one for your messages. There are five classes of messages: FIXME Messages in this class are meant to signal unimplemented features, known bugs, etc. They serve as a constant and active reminder of what needs to be done. ERR Messages in this class indicate serious errors in Wine, such as as conditions that should never happen by design. WARN These are warning messages. You should report a warning when something unwanted happens, and the function can not deal with the condition. This is seldomly used since proper functions can usually report failures back to the caller. Think twice before making the message a warning. TRACE These are detailed debugging messages that are mainly useful to debug a component. These are turned off unless explicitly enabled. MESSAGE There messages are intended for the end user. They do not belong to any channel. As with warnings, you will seldomly need to output such messages. Each component is assigned a debugging channel. The identifier of the channel must be a valid C identifier (reserved word like int or static are premitted). To use a new channel, simply use it in your code. It will be picked up automatically by the build process. Typically, a file contains code pertaining to only one component, and as such, there is only one channel to output to. You can declare a default chanel for the file using the WINE_DEFAULT_DEBUG_CHANNEL() macro: #include "wine/debug.h" WINE_DEFAULT_DEBUG_CHANNEL(xxx); ... FIXME("some unimplemented feature", ...); ... if (zero != 0) ERR("This should never be non-null: %d", zero); ... In rare situations there is a need to output to more than one debug channel per file. In such cases, you need to declare all the additional channels at the top of the file, and use the _-version of the debugging macros: #include "wine/debug.h" WINE_DEFAULT_DEBUG_CHANNEL(xxx); WINE_DECLARE_DEBUG_CHANNEL(yyy); WINE_DECLARE_DEBUG_CHANNEL(zzz); ... FIXME("this one goes to xxx channel"); ... FIXME_(yyy)("Some other msg for the yyy channel"); ... WARN_(zzz)("And yet another msg on another channel!"); ... To test whether the debugging channel xxx is enabled, use the TRACE_ON, WARN_ON, FIXME_ON, or ERR_ON macros. For example: if(TRACE_ON(atom)){ ...blah... } You should normally need to test only if TRACE_ON, all the others are very seldomly used. With careful coding, you can avoid the use of these macros, which is generally desired. Resource identifiers can be either strings or numbers. To make life a bit easier for outputting these beasts (and to help you avoid the need to build the message in memory), I introduced a new function called debugres. The function is defined in wine/debug.h and has the following prototype: LPSTR debugres(const void *id); It takes a pointer to the resource id and returns a nicely formatted string of the identifier (which can be a string or a number, depending on the value of the high word). Numbers are formatted as such: #xxxx while strings as: 'some-string' Simply use it in your code like this: #include "wine/debug.h" ... TRACE("resource is %s", debugres(myresource)); Many times strings need to be massaged before output: they may be NULL, contain control characters, or they may be too long. Similarly, Unicode strings need to be converted to ASCII for usage with the debugging API. For all this, you can use the debugstr_[aw]n? familly of functions: HANDLE32 WINAPI YourFunc(LPCSTR s) { FIXME("(%s): stub\n", debugstr_a(s)); } It is possible to turn on and off debugging output from within the debugger using the set command. Please see the WineDbg Command Reference section for how to do this. The WINEDEBUG environment variable controls the output of the debug messages. It has the following syntax: WINEDEBUG= [yyy]#xxx[,[yyy1]#xxx1]* where # is either + or - when the optional class argument (yyy) is not present, then the statement will enable(+)/disable(-) all messages for the given channel (xxx) on all classes. For example: WINEDEBUG=+reg,-file enables all messages on the reg channel and disables all messages on the file channel. when the optional class argument (yyy) is present, then the statement will enable (+)/disable(-) messages for the given channel (xxx) only on the given class. For example: WINEDEBUG=trace+reg,warn-file enables trace messages on the reg channel and disables warning messages on the file channel. also, the pseudo-channel all is also supported and it has the intuitive semantics: WINEDEBUG=+all -- enables all debug messages WINEDEBUG=-all -- disables all debug messages WINEDEBUG=yyy+all -- enables debug messages for class yyy on all channels. WINEDEBUG=yyy-all -- disables debug messages for class yyy on all channels. So, for example: WINEDEBUG=warn-all -- disables all warning messages. Also, note that at the moment: the FIXME and ERR classes are enabled by default the TRACE and WARN classes are disabled by default To compile out the debugging messages, provide configure with the following options: --disable-debug -- turns off TRACE, WARN, and FIXME (and DUMP). --disable-trace -- turns off TRACE only. This will result in an executable that, when stripped, is about 15%-20% smaller. Note, however, that you will not be able to effectively debug Wine without these messages. This feature has not been extensively tested--it may subtly break some things. This new scheme makes certain things more consistent but there is still room for improvement by using a common style of debug messages. Before I continue, let me note that the output format is the following: yyy:xxx:fff <message> where: yyy = the class (fixme, err, warn, trace) xxx = the channel (atom, win, font, etc) fff = the function name these fields are output automatically. All you have to provide is the <message> part. So here are some ideas: do not include the name of the function: it is included automatically if you want to output the parameters of the function, do it as the first thing and include them in parentheses, like this: TRACE("(%d, %p, ...)\n", par1, par2, ...); for stubs, you should output a FIXME message. I suggest this style: FIXME("(%x, %d, ...): stub\n", par1, par2, ...); try to output one line per message. That is, the format string should contain only one \n and it should always appear at the end of the string. (there are many reasons for this requirement, one of them is that each debug macro adds things to the beginning of the line) if you want to name a parameter, use = : FIXME("(fd=%d, file=%s): stub\n", fd, name);