[wdmaudiodev] Re: kernel debbuging: -problem and question

  • From: "Juicehifi" <bernt@xxxxxxxxxxxxx>
  • To: <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Tue, 18 Dec 2007 03:44:01 +0100

Thank you,


How long pause is to be expected (1,87 Gb Pentium M)?


Do I have to do something before rebooting in order for the computer to find
the kernel debugger.


Best regards / vennlig hilsen





From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Tim Roberts
Sent: 18. desember 2007 03:35
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: kernel debbuging: -problem and question


Juicehifi wrote: 

Hello there,


Just started to look at drivers.


I am trying to boot the computer in debug mode. Just before it has
initialized all processes it hangs. Norton is the main suspect. Anyone knows
about this?

What do you mean, exactly, by "boot the computer in debug mode"?  Do you
mean you set /debug in boot.ini (or with bcdedit)?  Remember that this will
give a long pause at boot time while it tries to locate a kernel debugger.

Further; I am trying to set up a debug environment for PCI and MSVAD. In
windbg helpfile there is a double message: You have to use two computers /
you can do ?local? kernel debugging. Which is correct?

Both.  You can do local kernel debugging, and you can examine memory while
doing so, but you can't set breakpoints and you can't catch blue screens.
That severely limits its usefulness for hardware debugging.  For a piece of
hardware, you will certainly want to use two-machine debugging.

Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.

Other related posts: