Prev: .reload command in windbg
Next: Accessing display resolution in BIOS
From: PRANAV KANT GAUR on 25 Mar 2010 12:58
I am trying to locally debug my driver on vista SP2(32-bit).To enable
it,it(windbg) asks to execute:
bcdedit -debug on
and restart,but it appears to have no effect as even after executing(with
admin privileges) & restarting,it(windbg) still displays 'local kernel
debugging isn't enabled on this system'& instructs to execute
bcdedit -debug on
to enable it.

then how this configuration can actually be performed?
From: Don Burn on 25 Mar 2010 13:10
Local kernel debugging is almost worthless. You cannot set breakpoints,
you cannot monitor debug output, so why bother? You need to get a virtual
environment or a separate test machine.


Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr




> -----Original Message-----
> From: PRANAV KANT GAUR [mailto:PRANAVKANTGAUR(a)discussions.microsoft.com]
> Posted At: Thursday, March 25, 2010 12:58 PM
> Posted To: microsoft.public.development.device.drivers
> Conversation: local kernel debugging problem
> Subject: local kernel debugging problem
>
> I am trying to locally debug my driver on vista SP2(32-bit).To enable
> it,it(windbg) asks to execute:
> bcdedit -debug on
> and restart,but it appears to have no effect as even after
> executing(with
> admin privileges) & restarting,it(windbg) still displays 'local kernel
> debugging isn't enabled on this system'& instructs to execute
> bcdedit -debug
> on to enable it.
>
> then how this configuration can actually be performed?
>
>
> __________ Information from ESET Smart Security, version of virus
> signature
> database 4974 (20100325) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>

 | 
Pages: 1
Prev: .reload command in windbg
Next: Accessing display resolution in BIOS