Which part of the system is stopped during the kernell debugging?

From: Martin <martin.ghazaryan@xxxxxxxxx>
Date: Thu, 18 Oct 2007 00:33:32 -0700

Hi.

I wonder what is stopped in the target system during kernel debugging,
when we break into its code. I can see the system is frozen, does it
mean all threads are paused? And when we step through the code, which
thread in the system are we tracing?

Any explanations will be appreciated

Martin

.

Follow-Ups:
- Re: Which part of the system is stopped during the kernell debugging?
  - From: Günter Prossliner

Prev by Date: Re: FlushFileBuffers in non-privileged user mode
Next by Date: Re: Which part of the system is stopped during the kernell debugging?
Previous by thread: MsgWaitForMultipleObjects - The Saga Continues...
Next by thread: Re: Which part of the system is stopped during the kernell debugging?
Index(es):
- Date
- Thread

Relevant Pages

Question: PCI.SYS
... Let's say my target system has a 1394 adapter behind a PCI-PCI bridge, ... the kernel debugging has been enabled on the target's 1394 card. ...
(microsoft.public.development.device.drivers)
Re: Question: PCI.SYS
... > Let's say my target system has a 1394 adapter behind a PCI-PCI bridge, ... > the kernel debugging has been enabled on the target's 1394 card. ... > Calvin Guan Software Engineer ...
(microsoft.public.development.device.drivers)
Re: Kernel debug with windbg
... > Is it only possible to start kernel debugging as the target system boots ... > or can you attach to the target system after it has booted? ...
(microsoft.public.win32.programmer.kernel)
Kernel debug with windbg
... Is it only possible to start kernel debugging as the target system boots or can you attach to the target system after it has booted? ...
(microsoft.public.win32.programmer.kernel)