fix: use correct Windows API module Win32::System::Diagnostics::Debug for GetThreadContext

GetThreadContext, CONTEXT, CONTEXT_CONTROL, and CONTEXT_DEBUG_REGISTERS are in Win32::System::Diagnostics::Debug, not in Win32::System::Kernel. Updated all imports to use the correct module path.
This commit is contained in:
pandaadir05
2025-11-21 15:10:49 +02:00
parent 748e3b8f50
commit 8047998576

View File

@@ -284,7 +284,7 @@ mod platform {
pid: u32,
memory_regions: &[crate::MemoryRegion],
) -> Result<super::ThreadHijackingResult> {
use windows::Win32::System::Kernel::GetThreadContext;
use windows::Win32::System::Diagnostics::Debug::GetThreadContext;
use windows::Win32::System::Threading::{
OpenProcess, ResumeThread, SuspendThread, PROCESS_QUERY_INFORMATION, PROCESS_VM_READ,
THREAD_GET_CONTEXT, THREAD_SUSPEND_RESUME,
@@ -321,7 +321,7 @@ mod platform {
// Get thread context (registers)
#[cfg(target_arch = "x86_64")]
{
use windows::Win32::System::Kernel::{CONTEXT, CONTEXT_CONTROL};
use windows::Win32::System::Diagnostics::Debug::{CONTEXT, CONTEXT_CONTROL};
let mut context = CONTEXT {
ContextFlags: CONTEXT_CONTROL,
@@ -610,7 +610,7 @@ mod platform {
/// Detect hardware breakpoints by examining debug registers (DR0-DR7)
pub fn detect_hardware_breakpoints(pid: u32) -> Result<super::HardwareBreakpointResult> {
use windows::Win32::System::Kernel::{GetThreadContext, CONTEXT, CONTEXT_DEBUG_REGISTERS};
use windows::Win32::System::Diagnostics::Debug::{GetThreadContext, CONTEXT, CONTEXT_DEBUG_REGISTERS};
use windows::Win32::System::Threading::{
ResumeThread, SuspendThread, THREAD_GET_CONTEXT, THREAD_SUSPEND_RESUME,
};