windbg problem - solved

Thanks to the many folks who helped solve my windbg problem.

I’m almost too embarrassed to tell you the solution.

It turns out I was attempting to debug my CHECKED build on a FREE install of
win2000.
When I compiled my driver for the FREE environment, windbg was happy.

What was most confusing and frustrating about this is that it all used to
work in NT4, under the old windbg.

Again, thanks to all who helped. I’ll try not to pester this list with too
many more stupid questions :slight_smile:

-bill
Bill Christie
Link Engineering Company
Plymouth, Michigan, 48170

www.linkeng.com

>

Thanks to the many folks who helped solve my windbg problem.

I’m almost too embarrassed to tell you the solution.

It turns out I was attempting to debug my CHECKED build on a
FREE install of
win2000.
When I compiled my driver for the FREE environment, windbg was happy.

What was most confusing and frustrating about this is that it
all used to
work in NT4, under the old windbg.

I debug checked drivers under the free os w2k all the time and it works just
fine.

Mark Roddy
xxxxx@hollistech.com
www.hollistech.com
WindowsNT Windows 2000 Consulting Services

Yeah…
I thought that was it, but my checked build now mysteriously works too.
I sure wish I understood all the voodoo hocus-pocus. I’ve spent the better
part of 2 days trying to track down this problem. I waded through the .PDB
info, the makefile.def stuff, all the compiler and linker options, not to
mention the windbg docs.
Perhaps in my desperation to get everything working, I deleted the right
combination of files, changed the right switches… who knows?
someday I’ll understand this stuff… maybe…
-bill

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roddy, Mark
Sent: Tuesday, December 12, 2000 2:40 PM
To: NT Developers Interest List
Subject: [ntdev] RE: windbg problem - solved

>
> Thanks to the many folks who helped solve my windbg problem.
>
> I’m almost too embarrassed to tell you the solution.
>
> It turns out I was attempting to debug my CHECKED build on a
> FREE install of
> win2000.
> When I compiled my driver for the FREE environment, windbg was happy.
>
> What was most confusing and frustrating about this is that it
> all used to
> work in NT4, under the old windbg.

I debug checked drivers under the free os w2k all the time and it
works just
fine.

Mark Roddy
xxxxx@hollistech.com
www.hollistech.com
WindowsNT Windows 2000 Consulting Services


You are currently subscribed to ntdev as: xxxxx@linkeng.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

If you are using the standard build process then the only reasons I know of
for having problems with local variables are: 1) windbag insanity, like the
released (1.xx.xx) new windbag had a problem with some specific kinds of
local variables; 2) user error, as in pointing windbag at the wrong
symbols/executibles for the target system; 3) partial builds when switching
from checked to free driver versions (but only with the NT4 build process.)

This assumes that you are using the !new !improved windbag rather that the
one that ships with the ddk as the one that ships with the ddk is FUBAR.

If you aren’t using the standard build process for drivers, then what can I
say, do yourself a favor and stop doing that.

Mark Roddy
Windows 2000/NT Consultant
Hollis Technology Solutions
www.hollistech.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Bill Christie
Sent: Tuesday, December 12, 2000 3:43 PM
To: NT Developers Interest List
Subject: [ntdev] RE: windbg problem - solved

Yeah…
I thought that was it, but my checked build now mysteriously works too.
I sure wish I understood all the voodoo hocus-pocus. I’ve spent the better
part of 2 days trying to track down this problem. I waded
through the .PDB
info, the makefile.def stuff, all the compiler and linker options, not to
mention the windbg docs.
Perhaps in my desperation to get everything working, I deleted the right
combination of files, changed the right switches… who knows?
someday I’ll understand this stuff… maybe…
-bill

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Roddy, Mark
> Sent: Tuesday, December 12, 2000 2:40 PM
> To: NT Developers Interest List
> Subject: [ntdev] RE: windbg problem - solved
>
>
> >
> > Thanks to the many folks who helped solve my windbg problem.
> >
> > I’m almost too embarrassed to tell you the solution.
> >
> > It turns out I was attempting to debug my CHECKED build on a
> > FREE install of
> > win2000.
> > When I compiled my driver for the FREE environment, windbg was happy.
> >
> > What was most confusing and frustrating about this is that it
> > all used to
> > work in NT4, under the old windbg.
>
> I debug checked drivers under the free os w2k all the time and it
> works just
> fine.
>
>
> Mark Roddy
> xxxxx@hollistech.com
> www.hollistech.com
> WindowsNT Windows 2000 Consulting Services
>
> —
> You are currently subscribed to ntdev as: xxxxx@linkeng.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: xxxxx@wattanuck.mv.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com