pydia
The ultimate Python wrapper for the Microsoft's DIA SDK (Debug Interface Access)
Goal
pydia aims to ease the manual handling of PDB files. No more hacking together some IDA-Python - you can now use your favorite python ditribution and simply install a package! pydia makes all the common functionality used when working with PDB files extremely accessible.
My future vision
Hopefully, we can make pydia so powerful we will be able to accurately recreate header files from PDBs alone.
How?
The ideaology of pydia is as follows:
- Every DIA2 SDK COM function is wrapped by a neat C++ function which handles all memory allocation/de-allocation and reference count tracking. These C++ wrappers are found in DiaLib.
- Each DIA2 SDK "class" is implemented as a C-API Python class in pydia (the sub-project).
- The C-Python wrapper will never directly call a COM function - rather it will call a DiaLib method which will wrap the low level memory managment.
- The C-Python wrappings (pydia) must be as user-friendly and safe as possible. It should be actively difficult to missuse pydia's exported Python API.
- The DiaLib wrappings should be 100% responsible for all low-level management - especially memory-wise. Unless the user is a dehydrated donkey they should not be able to cause DiaLib to "seg-fault" (0xC0000005 -
STATUS_ACCESS_VIOLATION).
Internals
Directory structure
- CTests
- Testing framework for DiaLib based on Microsoft's CppUnitTestFramework.
- Resources
- Generally useful binary/misc resources for tests.
- DiaLib
- Implementation of the C++ wrapper library for the DIA2 SDK.
- PyTests
- Testing framework for pydia (the C-API Python module) based on pytest.
- pydia
- Implementation of the C-API Python module which wraps DiaLib (and by transitivity also the DIA2 SDK)
Installation
pydia is Windows-only (x64) and currently targets CPython 3.12.
pip install pydia3
The package is published as pydia3 but imported as pydia. The DIA runtime
(msdia140.dll) must be registered on the machine; it ships with Visual Studio
(<VS install>\DIA SDK\bin\amd64\msdia140.dll). If it isn't registered, run from
an elevated prompt:
regsvr32 "<VS install>\DIA SDK\bin\amd64\msdia140.dll"
Usage
import pydia
from pydia import DataSource
# Accepts a .pdb, or a binary whose PDB can be found via the symbol path.
data_source = DataSource(r"C:\Windows\System32\ntdll.dll")
for enum in data_source.get_symbols(pydia.SymTag.Enum):
print(enum.get_name(), enum.get_length(), enum.get_values())
for udt in data_source.get_symbols(pydia.SymTag.UDT):
print(udt.get_name())
for member in udt.enumerate_members():
print(" ", member.get_name(), hex(member.get_offset()))
See Examples/Python/ntdll_header_builder.py for a full example that rebuilds C headers (enums and structs) from PDBs, and PyTests for more API usage.
Building from source
Prerequisites
- Windows x64.
- Visual Studio 2022 with the Desktop development with C++ workload (this
includes the DIA SDK, at
<VS install>\DIA SDK). - CPython 3.12 x64 (python.org installer), including its headers and import libraries.
Build
From a Developer PowerShell for VS 2022:
# Where Python 3.12 is installed (defaults to C:\Python312).
$env:PYTHON_HOME = python -c "import sys; print(sys.base_prefix)"
# Optional: only needed if the DIA SDK isn't at <VS install>\DIA SDK.
# $env:DIA_SDK_DIR = "C:\path\to\DIA SDK"
msbuild pydia.sln /m /p:Configuration=Release-3.12 /p:Platform=x64 /t:pydia
Alternatively, open pydia.sln in Visual Studio and build the Release-3.12 | x64
configuration. The build produces pydia.pyd and stages a ready-to-package
folder at x64\Release-3.12\package.
Build and install a wheel
cd x64\Release-3.12\package
python -m pip install build
python -m build
python -m pip install (Get-ChildItem dist\*.whl).FullName
python -c "import pydia; print(pydia.DataSource)"
Running the tests
python -m pip install pytest
$env:PYTHONPATH = "$PWD\x64\Release-3.12\package"
python -m pytest
The C++ tests in CTests use the Microsoft CppUnitTestFramework and run from
Visual Studio's Test Explorer.
Linting
python -m pip install -r requirements-dev.txt
python -m ruff check .
python -m ruff format --check .
Metadata
Release files for pydia3 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pydia3-0.2.0.tar.gz | 117.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pydia3-0.2.0-cp312-cp312-win_amd64.whl | CPython 3.12 | CPython 3.12 | Windows x86-64 | Details |
Total release size: 230.5 kB
Release files / pydia3-0.2.0.tar.gz
| Download URL | pydia3-0.2.0.tar.gz |
|---|---|
| Size | 117.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba1610b3da65f53545002cbc9db4cb601597e50beb0efa05c4cd309af7098128
|
|
BLAKE2b-256 checksum How to use checksums |
a85b02ba4811803bbd2108d328ebcf9bd71d0615b336fe9933b379ff8adcdb07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logRelease files / pydia3-0.2.0-cp312-cp312-win_amd64.whl
| Download URL | pydia3-0.2.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 113.4 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
53fd1f6862426e21a988a5c79790f5abe94bb31926f59da1f89e408bb311c17c
|
|
BLAKE2b-256 checksum How to use checksums |
7725bb3aa473fbfcfb3867b2c76f0a334e1c2f9513624f490969628857492754
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency log