-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Closed
Labels
bugThe issue describes a bug. It does not mean the bug has been reproduced by a developer.The issue describes a bug. It does not mean the bug has been reproduced by a developer.
Description
Operating System
Windows 11
x64dbg Version
[snapshot_2025-07-04_16-03]
(https://github.com/x64dbg/x64dbg/releases/download/2025.06.30/snapshot_2025-07-04_16-03.zip)
Describe the issue
🐛 Plugin SDK: Incomplete libraries in snapshot 2025-07-04 causing build failures
Problem Description
Plugin developers are experiencing linker errors when building plugins with the latest x64dbg SDK snapshot (2025-07-04_16-03). The SDK libraries appear to be incomplete or corrupted, missing essential plugin symbols for both x32 and x64 architectures.
Environment
- x64dbg Version: snapshot_2025-07-04_16-03
- Build System: CMake + Visual Studio 2022
- Plugin SDK: From latest snapshot download
Issue Details
Library Size Comparison
The newer SDK contains significantly smaller libraries compared to stable versions for both architectures:
Working SDK (snapshot_2025-03-15):
x64dbg.lib
: ~111KB (contains plugin symbols)x64bridge.lib
: ~48KBx32dbg.lib
: ~85KB (contains plugin symbols)x32bridge.lib
: ~49KB
Broken SDK (snapshot_2025-07-04):
x64dbg.lib
: ~2KB ❌ (missing symbols)x64bridge.lib
: ~57KBx32dbg.lib
: ~2KB ❌ (missing symbols)x32bridge.lib
: ~58KB
Linker Errors with New SDK
Both x32 and x64 plugin builds fail with identical `errors:```
Steps to reproduce
Root Cause Analysis
- Headers are complete - all function declarations present for both architectures
- Core libraries are incomplete - both
x32dbg.lib
andx64dbg.lib
missing symbol implementations - Bridge libraries seem intact -
x32bridge.lib
andx64bridge.lib
sizes are normal - The issue appeared between 2025-03-15 (working) and 2025-07-04 snapshots
- Affects both architectures - not platform-specific issue
Metadata
Metadata
Assignees
Labels
bugThe issue describes a bug. It does not mean the bug has been reproduced by a developer.The issue describes a bug. It does not mean the bug has been reproduced by a developer.