Pybag
Python bindings for Microsoft DbgEng
Pybag provides helper functions on top of Python bindings for Microsoft Debug Engine to facilitate Windows native debugging.
Installation
Install the Debugging Tools
- From the Windows SDK here: https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/
- From the App Store
- Directly: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/#install-windbg-directly
pip install pybag
Usage example
Use Python's repl as a command shell if desired. Ctrl-c will break-in to the debugger if you are in a wait() call.
Local user debugging
from pybag import *
def handler(bp, dbg):
print("*********** BREAK")
return DbgEng.DEBUG_STATUS_GO
dbg = UserDbg()
dbg.create("notepad.exe")
dbg.bp("Kernel32!WriteFile", handler)
dbg.go()
Remote user debugging
from pybag import *
def handler(bp, dbg):
print("*********** BREAK")
return DbgEng.DEBUG_STATUS_GO
dbg = UserDbg()
d.connect("tcp:server=192.168.1.10,port=5555")
dbg.create("notepad.exe")
dbg.bp("Kernel32!WriteFile", handler)
dbg.go()
Remote kernel debugging
from pybag import *
k = KernelDbg()
k.attach("net:port=50000,key=1.2.3.4")
Release History
- 2.2.16
- Bugfix for comtypes change
- 2.2.15
- Implementation of exception related calls
- 2.2.14
- Bug fix for breakpoints
- Switched to py-win32more for thread CONTEXT
- 2.2.13
- Improved discovery of Windbg installation detection. Works with App store installations now.
- 2.2.12
- Fix #22 - comtypes issue
- 2.2.11
- Fix #18 - Fix SetImplicitProcessDataOffset
- Fix #19 - Implement CreateProcess2
- 2.2.10
- Better search for Windbg DLLs using registry and allowing user override
- 2.2.9
- Add implementations of GetCurrentThreadSystemId and GetProcessIdsByIndex
- 2.2.8
- Fixed missing files install issue
- 2.2.7
- Fixed access violation when using oneshot breakpoints
- Added 'count' option to breakpoints
- 2.2.6
- Added support for more dbgeng calls
- Symbol handling
- Set / get thread contexts
- Fixed ds command
- Added support for more dbgeng calls
- 2.2.5
- Fixed be command
- Better search for Windbg install (and DLLs)
- 2.2.4
- Fixed lint issues
- 2.2.3
- Bug fix in WriteVirtual
- 2.2.2
- Python bindings rewritten to use comtypes
- Moved to Python 3
- Support multiple debugging uses
- Local user debugging
- Remote kernel debugging
- Remote user debugging using dbgsrv
Meta
Distributed under the MIT license. See LICENSE for more information.
Metadata
Release files for Pybag 2.2.16
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pybag-2.2.16.tar.gz | 152.9 kB | Without provenance | Details for pybag-2.2.16.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pybag-2.2.16-py3-none-any.whl | Python 3 | none | any | Details for pybag-2.2.16-py3-none-any.whl |
Total release size: 311.9 kB
Release files / pybag-2.2.16.tar.gz
| Download URL | pybag-2.2.16.tar.gz |
|---|---|
| Size | 152.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
64066f4e5c6581fa9cf778d8e6cf5ce33d3f431961557365c465905ca79b2966
|
|
BLAKE2b-256 checksum How to use checksums |
e1841053510186c0f9a37daad1287194c1b57167590fb065f33ed2d481db58e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Release files / pybag-2.2.16-py3-none-any.whl
| Download URL | pybag-2.2.16-py3-none-any.whl |
|---|---|
| Size | 158.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cef631e87d0bb12163c8cb11ca756ddfa8924a6eacdbd746683ed58948a2bfdf
|
|
BLAKE2b-256 checksum How to use checksums |
5ea252084698c0a3c7e7a94ddfff26f83df09a50781b8436f6f203f5de0a457c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Security for Pybag 2.2.16
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.