Thanks for the feedback:
Tabs — I finally figured out that if I multiply by 4 I could
get
We will get this fixed.
Ctrl-Break message
I assume you mean what appears when someone hits
ctrl-c/ctrl-break while kernel debugging.
You can turn that off by defining the env var KDQUIET
and set it equal to anything. Then start windbg with this defined & you
will not see the message. We will update the docs on this.
Local labels
We will improve the docs on this point. Also remember
that optimized code does whatever it wants with your locals & the
debugger is not given enough information to make complete sense of it.
So source level debug unoptimized code if possible.
Why do all those “Save ??? workspace” queries pop up when
If you hit “Yes” to one then you shouldn’t get them near
as much. We know about this and are improving it.
Oddly enough, I miss the C structuring colors … I hope they are
added back
Go back to Green for a breakpoint hit, yellow for stepping, and
We will look into this
-----Original Message-----
From: Gary Little [mailto:xxxxx@delphieng.com]
Sent: Tuesday, June 13, 2000 12:16 PM
To: NT Developers Interest List
Subject: [ntdev] RE: New test release of WinDBG
Nathan,
Thank you. Big improvement. I’ve been using it for several hours and so
far
NO crashes, and .reboot WORKS!!! The only real problems I’ve had have
been
related to procedure and command changes, and those have been resolved
in
the documentation. I’ve detailed below some of the things I’ve found. If
it
continues to function, I’ll be removing the other pieces of crap I’ve
been
using.
Oh, I’m using it to debug an NT device driver on a Dual Processor, using
NT
4.0, SP4.
I like the way the Locals window is grayed out but retains the last
valid
data for review. In fact there is several things I like.
Caveats:
Absolutely, read the manual. If you’re in a hurry,
looking
at “Installation and set up” is a must or your going to start slapping
your
keyboard and cussing developers that like to change existing interfaces.
Pain in the butt:
Tabs — I finally figured out that if I multiply by 4 I could
get
my code to line up properly.
Hopefully you will fix it such that 1 tab stop equals 1
character.
Ctrl-Break message
Give me a means of making it go away (I may have missed
it
in the docs, however)
Local labels
Did not at first appear, at all, period!!! Went stomping
back through the documentation muttering nasty
comments, and finally figured out that I needed to
generate
a pdb file. Wonderful, how do you do that!? So
now into the VC++ documentation and finally found that
you
do that by setting the check boxes in the Linker
tab in the Settings dialog.
Why do all those “Save ??? workspace” queries pop up
when
you do a .reboot? I’m rebooting the remote, not quitting WinDBG. It’s a
pain
because sometimes I need to empty my elderly bladder while the target
system
reboots.
Wish list:
Oddly enough, I miss the C structuring colors … I hope they are added
back
before release.
Other color changes …
Go back to Green for a breakpoint hit, yellow for stepping, and
magenta for a non instantiated break-point.
Gary
-----Original Message-----
From: Gary Little [mailto:xxxxx@delphieng.com]
Sent: Tuesday, June 13, 2000 9:08 AM
To: NT Developers Interest List
Subject: [ntdev] RE: New test release of WinDBG
Just downloaded and installed it. Since I’m in a very
heavy
debug session,
and neither 2127 or the Sep 99 versions I’m using are
worth
using as
toilette paper, I’m really hoping this will work.
all fingers>.
We shall see what we shall see …
-----Original Message-----
From: Nathan Nesbit
[mailto:xxxxx@Exchange.Microsoft.com]
Sent: Tuesday, June 13, 2000 8:49 AM
To: NT Developers Interest List
Subject: [ntdev] New test release of WinDBG
-----Original Message-----
From: Andre Vachon
My team has just released a new test version of WinDBG
on
http://www.microsoft.com/ddk/debugging
http:
We have done some major work on the UI, reenabling all
the
important
features that were missing from the WinHEC release.
We have added a number of new debugger commands, and
fixed a
lot of bugs
reported by our internal users.
We are acutally getting more internal usage of WinDBG
then
ever. Many of
the hardcore i386kd.exe users are now using WinDBG, and
we
have had very few
complaints (all of which have been fixed already)
So I really hope you will give it a try and give us some
feedback at
xxxxx@microsoft.com
We appreciate the good feeback but really want to hear
about
the bad. Don’t
get frustrated with the debugger - let us know about the
problems so we can
fix them !
I also encourage everyone to take a look through the
documentation.
I especially encourage advanced users to look through
the
reference section
for the debugger commands, as we have enhanced and added
many commands. A
number of commands have also changed from the old WinDBG
as
our command
syntax is based on i386kd.exe
If you find any bugs (even bugsin the documentation),
please
let us know -
we will do our best to get them fixed quickly.
Bugs, request for features, praise, complaints, etc :
send
mail to
xxxxx@microsoft.com
Thanks,
The WinDBG team.
—
You are currently subscribed to windbg as:
xxxxx@microsoft.com
To unsubscribe send a blank email to
xxxxx@lists.osr.com
—
You are currently subscribed to ntdev as:
xxxxx@delphieng.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’)</http:>
;