Re: Build device driver using Microsoft Visual C++ 2005

Tech-Archive recommends: Fix windows errors by optimizing your registry


"mirage2k2" <mirage2k2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B4A6CF3D-D3C9-4801-ADEE-31DBB8BDE399@xxxxxxxxxxxxxxxx
So if I do not use SoftIce, how will I step through my code? I know that
you
can do this with WinDbg using 2 machines, but this is the hardest and
slowest
way of doing this! Our company simply cannot afford to waste so much time
using this ancient technique. Is there an alternative? Have MS updated
WinDbg so that it will do this? Do they have any plans to?

Why is this the hardest and slowest? The advantage of two machines is that
you are doing minimal disturbance of the test system with the debugger. The
other big advantage is that you are not risking corruption of the
development environment with the driver, this latter is critical if you work
in the storage space.

WinDBG on two machines was never slow compared to SoftIce, and nowadays with
1394 debugging it flies. I have never found 2 machine debugging harder, and
with the .kdfiles capability in WinDBG (where the debugger intercepts the
load of the driver, and installs one from the development machine on the
test machine) thing really fly. In a lot of cases, I will find a stupid bug
in WinDBG that caused a crash, fix them on source, and compile while the
test machine is rebooting. If you ever have one crash that requires a
reinstall, the cost of the second machine is probably covered in the wasted
time.

I really have to refute the slowest claim, I have been charging extra if a
customer forces me to use SoftIce since my productivity was so much worse.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply



.

Relevant Pages

  • Re: question about oneys samples
    ... Don Burn pointed me to a windbg tutorial. ... there are 2 main debugger choices: ... > With WinDbg, in order to do single-stepping, you need a second machine. ... >> i am new to device drivers on windows, ...
    (microsoft.public.development.device.drivers)
  • Re: .kdfiles with boot start drivers on Vista
    ... Here is my output from WinDbg: ... BD: Boot Debugger Initialized ... I have seen several veteran driver devs ask this same ...
    (microsoft.public.development.device.drivers)
  • Re: Getting MAC Header Size from an Intermediate Driver
    ... Just to add to what Thomas already said, if you are a beginner in driver ... (windbg), analyze a crash dump and connect the debugger to a remote machine ...
    (microsoft.public.development.device.drivers)
  • Problem in debugging sample ioctl driver
    ... I was trying to practice debugging(through WINDBG) over ioctl sample driver ... 1.While trying to use deferred breakpoint for Driver Entry routine using ... On permitting debugger to search & load remaining symbols it displays: ...
    (microsoft.public.development.device.drivers)
  • Re: question about oneys samples
    ... there are 2 main debugger choices: ... With WinDbg, in order to do single-stepping, you need a second machine. ... > i am new to device drivers on windows, but have done driver programming on ...
    (microsoft.public.development.device.drivers)