Zebediah Figura z.figura12@gmail.com writes:
While this does avoid usually undesired debug output, it also makes debugging winedbg.exe practically impossible.
Yes, but that's a very uncommon use case. In 99.9% of the usage cases we don't want the winedbg traces to pollute the log.
IMO it's enough to simple apply your patch locally when you are working on winedbg, that's what I've been doing in such cases. If you really need a runtime mechanism, it would have to be something like what Ken has suggested.