[Bug 30573] New: Give kernel32.GlobalMemoryStatus(Ex) own/separate debug channel, different from +heap (ntdll)

http://bugs.winehq.org/show_bug.cgi?id=30573

Bug #: 30573
           Summary: Give kernel32.GlobalMemoryStatus(Ex) own/separate
                    debug channel, different from +heap (ntdll)
           Product: Wine
           Version: 1.5.3
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: kernel32
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
    Classification: Unclassified

Hello,

just an enhancement request.

.NET runtime makes extensive use of this API (-Ex version) to check resource
usage while doing CPU/memory-intensive jobs.
The same mechanism can also be found in some installers: Windows SDK 8 etc.

To track down reported memory usage problems I had to give that API (lives in
kernel32 heap.c) an own debug channel to see what is actually reported to
applications at runtime.

Using the default +heap channel for kernel32 heap.c also triggers ntdll's
heap.c and enables all sorts of unintended heap checking which is not what I
want in this situation (generates huge logs and makes things very slow - even
if I use a pipe for filtering).
It would also trigger kernel32.GlobalAlloc() traces.

If own/separated debug channel is not feasible - ok - just another patch in my
private repo.

Regards