Visual Studio 2005 hangs in kernel debug OS mode

NTDEV
1

When computer runs in kernel debugging mode, Visual Studio breaks in a kernel debugger. It is necessary to execute .go in WinDbg to continue.
I need to run developer computer in kernel debugging mode, without debugger attached. Every time when Visual Studio starts, computer hangs, since there is no kernel debugger to resume it. Is there any way to disable this feature, preventing Visual Studio to break in the kernel mode?

2

wrote in message news:xxxxx@ntdev…
> When computer runs in kernel debugging mode, Visual Studio breaks in a
> kernel debugger. It is necessary to execute .go in WinDbg to continue.
> I need to run developer computer in kernel debugging mode, without
> debugger attached. Every time when Visual Studio starts, computer hangs,
> since there is no kernel debugger to resume it. Is there any way to
> disable this feature, preventing Visual Studio to break in the kernel
> mode?
>

Try kdbctrl -du
kdbctrl.exe is in same directory where windbg is installed.

–pa

3

Thanks. I forgot to mention, that I need solution for Windows XP, and kdbgctrl requires at least Windows Server 2003.

4

Look at “sx” in the windbg docs.

Mm
On Aug 15, 2011 7:52 AM, wrote:
> Thanks. I forgot to mention, that I need solution for Windows XP, and
kdbgctrl requires at least Windows Server 2003.
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

5

mm - there is no debugger attached, I cannot use WinDbg commands.

6

On Mon, Aug 15, 2011 at 1:27 PM, wrote:
> mm - there is no debugger attached, I cannot use WinDbg commands.

Can you use livekd? And why do you need to be in debug mode on your
development system?

Kris

7

I need to have these computers ready for kernel debugging. Whan some event occurs, I want to connect with WinDbg and debug the drivers. Meanwhile, user mode developers should work as usual.
livekd is a good idea, but I don’t want to change the way user mode developers are working.

8

You really would be better served by just enabling KD on your test machines, not your development/build machines.

An alternative would be to use /crashdebug which enables KD only at bugcheck time. It wasn’t entirely clear why you need to have KD on your dev machines to begin with though (hopefully you are *not* using the same machine for both dev and test for kernel mode development).

  • S (Msft)

-----Original Message-----
From: xxxxx@yahoo.com
Sent: Monday, August 15, 2011 6:13
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Visual Studio 2005 hangs in kernel debug OS mode

I need to have these computers ready for kernel debugging. Whan some event occurs, I want to connect with WinDbg and debug the drivers. Meanwhile, user mode developers should work as usual.
livekd is a good idea, but I don’t want to change the way user mode developers are working.

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

9

>WinDbg and debug the drivers. Meanwhile, user mode developers should work as usual.

Use crash dumps and later analyze them.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com