[Bug 50665] New: Inconsistent behavior of kernel32.OutputDebugStringA/W API with regards to Wine 'debugstr' and 'seh' debug channel usage

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50665

Bug ID: 50665
           Summary: Inconsistent behavior of kernel32.OutputDebugStringA/W
                    API with regards to Wine 'debugstr' and 'seh' debug
                    channel usage
           Product: Wine
           Version: 6.2
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: kernel32
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Hello folks,

before commit
https://source.winehq.org/git/wine.git/commitdiff/3b002685fe18ca3985af744d8f...
("kernel32: Move debugger functions to kernelbase.") one could use 'debugstr'
channel facility for apps/drivers that make use of 'OutputDebugStringA/W' API
without all the other debug channels noise. Definitely helpful besides running
the app under a debugger or Sysinternal's 'DebugView' tool.

After that commit one had to use 'seh' debug channel and filter all the
unwanted messages to get a similar result.

With the fix for bug 48059 ("IMVU Social Network Client v539 hangs"), commit
https://source.winehq.org/git/wine.git/commitdiff/4ac3cbd6ccba52ad8d528ee745...
("kernel32: Duplicate OutputDebugStringA implementation.") to old 'debugstr'
debug channel got reintroduced again which leads to inconsistent behavior.

If the app calls 'OutputDebugStringA' - which only few do - one can still use
the old 'debugstr' channel but any 'OutputDebugStringW' calls won't be seen.
That's not very useful.

Either put 'OutputDebugStringA' into 'seh' debug channel or duplicate
'OutputDebugStringW' to kernel32.

$ wine --version
wine-6.2

Regards