Unrecognized process listed in "Attach to Process" under Debug in Visual Studio

NTDEV
1

I have a kernel mode driver installed on my target computer running Windows 10 64-bit, the goal is to use the kernel debugging engine in visual studio and attach to the installed driver but the option shown under “Debug”->“Attach To Process” is Kernel Debugger, remote computer name, and name of process. but the only process available is Kernel with ID 0. I expected to find the driver (.sys) to break into the debugger.

I have configured the remote computer for debugging and test framework prior to this step. Is there something that I’m missing that the kernel driver process is not appearing to attach the debugger to?

Thanks very much.

2

xxxxx@gmail.com wrote:

I have a kernel mode driver installed on my target computer running Windows 10 64-bit, the goal is to use the kernel debugging engine in visual studio and attach to the installed driver but the option shown under “Debug”->“Attach To Process” is Kernel Debugger, remote computer name, and name of process. but the only process available is Kernel with ID 0. I expected to find the driver (.sys) to break into the debugger.

Drivers are not processes. Drivers are just DLLs that happen to get
loaded into the system process. When you break in, you stop the entire
operating system. You then have the ability to set breakpoints in your
own driver.

I have configured the remote computer for debugging and test framework prior to this step. Is there something that I’m missing that the kernel driver process is not appearing to attach the debugger to?

There is no “kernel driver process”. When you attach a kernel debugger,
you are attaching to a system, not to a process.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

Just use standalone WinDbg instead of the bloated brontosaur called Visual Studio.

–
Maxim S. Shatskih
Microsoft MVP on File System And Storage
xxxxx@storagecraft.com
http://www.storagecraft.com

wrote in message news:xxxxx@ntdev…
>I have a kernel mode driver installed on my target computer running Windows 10 64-bit, the goal is to use the kernel debugging engine in visual studio and attach to the installed driver but the option shown under “Debug”->“Attach To Process” is Kernel Debugger, remote computer name, and name of process. but the only process available is Kernel with ID 0. I expected to find the driver (.sys) to break into the debugger.
>
> I have configured the remote computer for debugging and test framework prior to this step. Is there something that I’m missing that the kernel driver process is not appearing to attach the debugger to?
>
> Thanks very much.
>