Add new "nrelay" debug channel - useful for debugging GPFs in target applications

[Troy Rollo]

The nrelay ("native relay") debug channel acts to limit the output of the 
relay debug channel, and only works if the relay debug channel is also on. 
When "nrelay" is on, "relay" will not log calls made from one built-in 
library to another built-in library, or within a built-in library. Thus each 
call logged is a call made directly by the target application or by one of 
the native DLLs it depends on.

This produces much briefer output that is often more useful in identifying 
where target application is having problems.

Activate by setting WINEDEBUG=relay,nrelay

Alternatives considered but rejected:

 - Having a config file option. When the config file options are read it is
   already too late to prevent calls by and between kernel32.dll and
   ntdll.dll from being logged.

 - Having nrelay be independent of relay - this would involve making
   modifications almost everywhere that TRACE_ON(relay) was used,
   which did not seem to be warranted.

ChangeLog:
 Add an "nrelay" debug channel which, when on, limits logging of calls
 by the "relay" debug channel to calls by the made directly by a native
 EXE or DLL.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: nrelay.diff
Type: text/x-diff
Size: 4023 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-patches/attachments/20050302/4b360636/nrelay.bin