AARGH… I am using the new wndbg beta (5.1.2250.3).
Whenever I open a new window, I can’t get rid of it.
I’ve got something like 20 windows open now (source,
assembly, locals, watch,…). I close them all, and
then “save workspace”, but when I restart wndbg they
all come back again. It’s driving me crazy!!
Has anyone else had this problem or is my computer
the victim of some demonic posession?
The workspace mechanism is hosed. In addition to the arbitrary retention of
various windows, windbag also appears to suffer from the arbitrary retention
of breakpoint settings across reboots, including reboots with new driver
objects, thus leading to some rather odd target system behavior.
When in doubt, cut it out. A good surgeon always reaches for the knife. Go
to the registry and delete all that crufty workspace stuff from
HKLM\SOFTWARE\Microsoft\Windbg.
Those of us who follow the perils of windbag will remember that workspace
encrustation was a feature of the old windbag starting somewhere around 1998
or so. At least that version allowed one to simply set all options from the
command line and never actually use a workspace. This version appears to use
workspaces regardless of what you might do on the command line.
-----Original Message-----
From: Peter Craft [mailto:xxxxx@alacritech.com]
Sent: Friday, August 18, 2000 2:29 PM
To: NT Developers Interest List
Subject: [ntdev] wndbg windows: Make them go away!!!
AARGH… I am using the new wndbg beta (5.1.2250.3).
Whenever I open a new window, I can’t get rid of it.
I’ve got something like 20 windows open now (source,
assembly, locals, watch,…). I close them all, and
then “save workspace”, but when I restart wndbg they
all come back again. It’s driving me crazy!!
Has anyone else had this problem or is my computer
the victim of some demonic posession?
The breakpoint behaviour you are seeing is by design.
Obviously, you do not like the design, so we’ll see how we can change it.
-Andre
Andre,
We all appreciate the efforts being made to improve the quality of windbag.
However, the specific behavior being reported is not “by design”, it is a
defect, a bug. There may be features of the workspace management that some
of us don’t like, but that is not what was reported.
1a. for breakpoints the above problem can result in the inability to start
the target system or run the target system reliably.
windbag does not appear to detect correctly and/or reliably the
modification of a module that has breakpoints set in in across reboots
and/or driver unload/reload operations. This can result in the inability to
start or run the target system reliably. This appears to be related to 1a
above.
It does not appear that the dialog box that asks for confirmation of a
workspace save operation does anything. This may be related to (1) above.
There appears to be no way to start windbag with a clean set of
workspaces other than to manually purge the registry.
Keep those windbag updates coming!
-----Original Message-----
From: xxxxx@microsoft.com [mailto:xxxxx@microsoft.com]
Sent: Monday, August 21, 2000 7:32 AM
To: NT Developers Interest List
Subject: [ntdev] RE: wndbg windows: Make them go away!!!The breakpoint behaviour you are seeing is by design.
Obviously, you do not like the design, so we’ll see how we
can change it.-Andre
You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)