
                              Wine Documentation                               
Prev                       Chapter 8. Debug Logging                        Next
-------------------------------------------------------------------------------

Debugging channels

Also, we divide the debugging messages on a component basis. Each component is
assigned a debugging channel. The identifier of the channel must be a valid C
identifier but note that it may also be a reserved word like int or static.

Examples of debugging channels: reg, updown, string

We will refer to a generic channel as xxx.
   
   
    Note: for those who know the old interface, the channel/type is what
    followed the _ in the dprintf_xxx statements. For example, to output a
    message on the debugging channel reg in the old interface you would had to
    write:
    dprintf_reg(stddeb, "Could not access key!\n");                            
                                                                               
   
    In the new interface, we drop the stddeb as it is implicit. However, we add
    an orthogonal piece of information to the message: its class. This is very
    important as it will allow us to selectively turn on or off certain
    messages based on the type of information they report. For this reason it
    is essential to choose the right class for the message. Anyhow, suppose we
    figured that this message should belong in the WARN class, so in the new
    interface, you write:
    WARN(reg, "Could not access key!\n");                                      
                                                                               

-------------------------------------------------------------------------------
Prev                                 Home                                 Next
Debug Logging                         Up                         How to use it
