I agree with Mark and all of you about the shortages of WinDbag.
I have so much disappointment after so much investigation of time and nerve
into WinDbag, though Windbg Win 2000 RC2 till pre release NEW IMPROVED
Windbg, without success.
Now I am returning back since months to the primitive but successfull way of
driver debugging under Win2K as at the stone time of programming:
- With a properly design of the driver.
- With the use of DbgPrint and Russinovich?s DbgView
SoftICE is good but my methode is better enough to help me spare time and
nerve ($1300 ignored)
Huu Dung Nguyen
From: Mark Roddy[SMTP:xxxxx@hollistech.com]
Reply To: NT Developers Interest List
Sent: Friday, April 28, 2000 4:05 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Pre-release version of New Windbg available
So I went home after my frustrating experience with the NEW! IMPROVED!
windbag on NT4 SP6 that couldn’t even open a source file and tried it out
on
W2K B2195. Oh what a surprise, Open Source File works on that version of
Windows.
So fine, I can open a source file. And after depositing the pdb files into
the symbol path, which I never had to do before, I could actually set a
breakpoint from a source window! Wow! Too bad the breakpoint, and every
other breakpoint I set was totally non-functional.
My earlier comments remain confirmed. This is an atrocity. Don’t waste
your
time.
Mark Roddy
Windows 2000/NT Consultant
Hollis Technology Solutions
www.hollistech.com
Yeah, if you only have to work with drivers that load AFTER softice …
-----Original Message-----
From: Jamey Kirby [mailto:xxxxx@storagecraft.com]
Sent: Thursday, April 27, 2000 1:20 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Pre-release version of New
Windbg available
SoftIce rules!
Jamey
-----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Bill
Casey
> Sent: Thursday, April 27, 2000 1:16 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Pre-release version of New Windbg
available
>
>
> Your last para there is so ‘right on the money’ that it
boggles the mind.
>
> Bill
>
> == SCSI Adapters & VirtualSCSI Target Mode Libs ==
> Advanced Storage Concepts, Inc. (409) 744-2129
> 2720 Terminal Drive xxxxx@advstor.com
> Galveston, TX 77554 USA www.virtualscsi.com
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Jan
Bottorff
> Sent: Thursday, April 27, 2000 11:15 AM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Pre-release version of New Windbg
available
>
>
> >A pre-release version of the new NT debugging tools is
now available at
> http://www.microsoft.com/ddk/debugging/. This is the same
debugger
> package that is available at WinHEC that Andre Vashon
spoke about.
>
> I downloaded and played with this a bit. It looks pretty
questionable it
> will save me any time over struggling with the old WinDBG,
until it gets
> more mature. For example, QuickWatch for browsing
structures seems not to
> function. On the bright side, after a couple cycles of
booting, the new
> debugger eventually found the symbols for my driver, and
actually stopped
> at a breakpoint.
>
> Still just amazes me that a company could spend 2 billion
dollars on OS
> development and not have an extreemly great kernel
debugger,
> fully debugged
> BEFORE writing a zillion lines of new kernel code.
>
> - Jan
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@advstor.com
> To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
>
>
> —
> You are currently subscribed to ntdev as:
xxxxx@storagecraft.com
> To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
>
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
Oh, lighten up Mark. It was advertised as a pre-release. The real test will
be whether they will fix the bugs found in the pre-release, and end up giving us
a usable version, or they will continue moving the bugs around as they have in all
prior versions. [Of course, I’m betting that they are afraid of Numega suing
them if they produce a working version, and give it away for free. Therefore
they will continue to only give out pre-release versions. ]
And besides, if you were good, you’d be able to write software that would
work the first time, and you won’t need no stinking debugger…
-DH
PS. Even if it actually functioned as designed, why would you build a kernel
debugger that does not give you a useful stack trace when an illegal
address is referenced?
----- Original Message -----
From: “Mark Roddy”
To: “NT Developers Interest List”
Sent: Thursday, April 27, 2000 10:05 PM
Subject: [ntdev] Re: Pre-release version of New Windbg available
>
> So I went home after my frustrating experience with the NEW! IMPROVED!
> windbag on NT4 SP6 that couldn’t even open a source file and tried it out on
> W2K B2195. Oh what a surprise, Open Source File works on that version of
> Windows.
>
> So fine, I can open a source file. And after depositing the pdb files into
> the symbol path, which I never had to do before, I could actually set a
> breakpoint from a source window! Wow! Too bad the breakpoint, and every
> other breakpoint I set was totally non-functional.
>
> My earlier comments remain confirmed. This is an atrocity. Don’t waste your
> time.
>
>
> Mark Roddy
> Windows 2000/NT Consultant
> Hollis Technology Solutions
> www.hollistech.com
>
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@syssoftsol.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
>
Oh, lighten up Mark. It was advertised as a pre-release.
The real test will
be whether they will fix the bugs found in the pre-release,
and end up giving us
a usable version, or they will continue moving the bugs
around as they have in all
prior versions.
I’m all light and you’re all light too. The debugger sucks.
And speaking of fixing bugs, be sure to mail bugs you find to
xxxxx@microsoft.com with repro situation and version number, etc. If you
consider it a serious blocking issue, feel free to mail me as well.
For the record, the download site (2nd) below has the beta. It is meant to
work with NT4 and beyond.
Bill Stuart
Microsoft, Program Manager, Windows Systems Developer Support
engineering support for core software and hardware developers
http://support.microsoft.com/support/ddk - DDK support pages
http://www.microsoft.com/ddk/ - download DDK’s
http://www.microsoft.com/support/customer/develop.htm - Support options
http://www.microsoft.com/hwdev/ - general hardware development
http://www.microsoft.com/mswish/ - make a product wish - choose DDK
category
sort
-----Original Message-----
From: Dave Harvey [SMTP:xxxxx@syssoftsol.com]
Sent: Friday, April 28, 2000 10:07 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Pre-release version of New Windbg available
Oh, lighten up Mark. It was advertised as a pre-release. The real test
will
be whether they will fix the bugs found in the pre-release, and end up
giving us
a usable version, or they will continue moving the bugs around as they
have in all
prior versions. [Of course, I’m betting that they are afraid of Numega
suing
them if they produce a working version, and give it away for free.
Therefore
they will continue to only give out pre-release versions. ]
And besides, if you were good, you’d be able to write software that would
work the first time, and you won’t need no stinking debugger…
-DH
PS. Even if it actually functioned as designed, why would you build a
kernel
debugger that does not give you a useful stack trace when an illegal
address is referenced?
----- Original Message -----
From: “Mark Roddy”
> To: “NT Developers Interest List”
> Sent: Thursday, April 27, 2000 10:05 PM
> Subject: [ntdev] Re: Pre-release version of New Windbg available
>
>
> >
> > So I went home after my frustrating experience with the NEW! IMPROVED!
> > windbag on NT4 SP6 that couldn’t even open a source file and tried it
> out on
> > W2K B2195. Oh what a surprise, Open Source File works on that version of
> > Windows.
> >
> > So fine, I can open a source file. And after depositing the pdb files
> into
> > the symbol path, which I never had to do before, I could actually set a
> > breakpoint from a source window! Wow! Too bad the breakpoint, and every
> > other breakpoint I set was totally non-functional.
> >
> > My earlier comments remain confirmed. This is an atrocity. Don’t waste
> your
> > time.
> >
> >
> > Mark Roddy
> > Windows 2000/NT Consultant
> > Hollis Technology Solutions
> > www.hollistech.com
> >
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@syssoftsol.com
> > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@MICROSOFT.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> I’d have to agree. With SoftIce upwards of $1300 I’m pretty happy with
Windbg. Besides, as far as I’ve been told Softice can’t debug boot
drivers.
Yes, because it will be unable to load symbol files till the boot FS will be
up.
But:
- this is for DriverEntry only. Other functions will be OK.
- there is a workaround called IcePack which packs symbol tables to another
boot driver and makes them accessible for SI.
Max