[PATCH 1/5] kernel32: Don't clear WINEDEBUG in the debugger process.
z.figura12 at gmail.com
Wed Aug 15 09:39:55 CDT 2018
On 15/08/18 01:19, Alexandre Julliard wrote:
> Zebediah Figura <z.figura12 at 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.
It's an uncommon case, but it's still a valid one, and I've been stymed
by being unable to debug winedbg remotely (e.g.
https://bugs.winehq.org/show_bug.cgi?id=45369). If what Ken suggested is
acceptable, then I'll submit a patch for that instead.
More information about the wine-devel