Tools for diagnosing DLL dependency loading issues
Project description
DLL Diagnostic Tools
The 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.
Contents
Requirements and installation
The 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
dlldiag trace
command)
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.
Usage
The 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 docker
this subcommand generates a Dockerfile suitable for using thedlldiag
command inside a Windows container, allowing the user to optionally specify the base image to be used in the Dockerfile'sFROM
clause. 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 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.
Legal
Copyright © 2019, Adam Rehn. Licensed under the MIT License, see the file LICENSE for details.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distributions
Built Distribution
Hashes for dll_diagnostics-0.0.3-py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | e22748373b23dbf76c510d216c6186cf851341694792ccf2d3ba1cd62909b190 |
|
MD5 | 4263737e0806ee1d6cc38c267475a8a9 |
|
BLAKE2b-256 | 8c75bf54c9865cd76b112a40cd1a9da61c5d86b02c60d57eb40e43a43bedf7e9 |