DLL Diagnostic Tools
dlldiag command-line tool provides functionality to assist in identifying the DLL dependencies of an application or library and diagnosing dependency loading issues. It is primarily intended for use when migrating existing applications to Windows containers, where traditional GUI-based tools are unavailable. Identifying the minimal set of dependencies for an application facilitates a workflow where the required DLL files can be copied from the mcr.microsoft.com/windows base image into the mcr.microsoft.com/windows/servercore base image, thus maximising application compatibility whilst maintaining the minimum possible image size.
Requirements and installation
dll-diagnostics Python package requires the following:
- Python 3.5 or newer
- Windows Server 2016 or newer, or Windows 10 version 1607 or newer
- Microsoft Visual C++ Redistributable for Visual Studio 2015-2019
- Debugging Tools for Windows 10 (WinDbg) (only needed for running the
You can install the package by running the following command:
pip install dll-diagnostics
If you don't need the package on your host system then you can download a prebuilt container image from Docker Hub to start using the
dlldiag command inside a Windows container.
dlldiag command-line tool provides the following subcommands:
dlldiag deps: this subcommand lists the direct dependencies for a module (DLL/EXE) and checks if each one can be loaded. Delay-loaded dependencies are also listed, but indirect dependencies (i.e. dependencies of dependencies) are not.
dlldiag dockerthis subcommand generates a Dockerfile suitable for using the
dlldiagcommand inside a Windows container, allowing the user to optionally specify the base image to be used in the Dockerfile's
FROMclause. This is handy when you want to extend an existing image of your choice, rather than simply extending the Windows Server Core image as the prebuilt images from Docker Hub do.
dlldiag graphthis subcommand runs executable modules with an injected DLL that uses Detours to instrument calls to LoadLibrary() so the call hierarchy can be reconstructed. This is handy when you want to see which indirect dependencies are being loaded by an executable's direct dependencies or want to identify dependencies that are loaded programmatically at runtime.
dlldiag trace: this subcommand uses the Windows debugger to trace a LoadLibrary() call for a module (DLL/EXE) and provide detailed reports of the results. The trace makes use of the Windows kernel loader snaps feature to obtain fine-grained information, as discussed in Junfeng Zhang's blog post "Debugging LoadLibrary Failures". The trace captures information about both indirect dependencies and delay-loaded dependencies.
Copyright © 2019-2021, Adam Rehn. Licensed under the MIT License, see the file LICENSE for details.