This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 78%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
"Show Loader Snaps" is a very useful GFlag to investigate dependency issue of an application.
When using it, I will get the debug output of this flag in the Debug Output windows of Visual Studio 2022 - that is nice.
But when using the famous DebugView instead of a debug session in Visual Studio I don't get the output of "Show Loader Snaps" in DebugView.
Does DebugView support the output of "Show Loader Snaps"?
If not, why is that the case?
Searching the internet I found out, I'm not the only one who stumbled upon this issue.
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/show-loader-snaps
https://learn.microsoft.com/en-us/sysinternals/downloads/debugview
Hello Mario,
The documentation for DebugView says:
Under Windows 2000, XP, Server 2003 and Vista DebugView will capture:
- Win32 OutputDebugString
- Kernel-mode DbgPrint
- All kernel-mode variants of DbgPrint implemented in Windows XP and Server 2003
However the loader snap output does not match any of those cases. Using "sxe out" in a debugger to break on debug output, the top of the stack looks like:
ntdll!vDbgPrintExWithPrefixInternal
ntdll!LdrpLogDbgPrint
ntdll!LdrpLogInternal
ntdll!LdrLoadDll
KERNELBASE!LoadLibraryExW
So the output is produced in user mode and does not use OutputDebugString; that might explain why DebugView does not capture the output.
An alternative would be to use Event Tracing for Windows (ETW) to capture the same information (that would involve starting an ETW trace session with the ImageLoad provider (GUID {2cb15d1d-5fc1-11d2-abe1-00a0c911f518}) and setting a trace flag for the process in "Image File Execution Options" (TracingFlags = 4)).
Gary
Thanks Gary, that actually helped.