Windbg Beta Available

NTDEV
2

Is there a new WinDbg drop? My version is 5.1.2240.1.

-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@Exchange.Microsoft.com]
Sent: Monday, July 24, 2000 2:06 PM
To: NT Developers Interest List
Subject: [ntdev] Windbg Beta Available

Here is Andre’s mail about the latest debugger release.

<<[windbg] WinDBG BETA>>

A few notes:

To get the list of drivers being loaded during boot you need to turn
on “verbose” You can do this with the -v command line option.

There is an SDK that can be installed. It contains the new
interfaces that one can use to write more powerful extensions with. Using
this SDK one can access all functionality of the debugger, which is
implemented in dbgeng.dll. Basicly all Windbg does is gives a UI to
dbgeng.dll. This means that someone could write a replacement debugger UI &
get all debugger functionality from dbgeng.dll The interfaces are not in
the documentation yet, so you just have what is in the .h file. Future
releases are planned to have the documentation and samples.

You can turn off Workspace prompting with the -Q command line
option. It answers No to all workspace prompts. The idea is you would
setup your workspace and save it. Then tse the -Q option so you will always
load the workspace, but never change it.

There are now Save & Clear Workspace items in the File menu.

The UI is now hooked up to pick up the context changes done with
.trap, .thread, .cxr, etc… This means if you do a .thread the call stack,
locals and other windows will change.

You need to use PDB symbol files to get locals, etc…

Enjoy

Nathan Nesbit
Windows Debugger Team - http://dbg http:</http:>

3

Yes, we just posted the official beta 1 release. Here is the posting
from the Windbg mailing list:

We’ve released a new BETA version of WinDBG today on
http://www.microsoft.com/ddk/debugging

This drop contains
*lots of bug fixes.
*new commands, such as .trap, .thread, .cxr, .exr, .lastevent, .logfile,

bu, sd, sq – sorry, not all these commands are documented yet.
*more work on the UI, addressing some of the problems reported by
external
customers

Please take a look at the docs. There are still some things missing,
but
it’s we continue to put a lot of effort into them.

Please try it out and send feedback (good or bad) about the tools or the

docs to xxxxx@microsoft.com

–Sandy
-----Original Message-----
From: Gary Little [mailto:xxxxx@delphieng.com]
Sent: Monday, July 24, 2000 2:18 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Windbg Beta Available

Is there a new WinDbg drop? My version is 5.1.2240.1.

-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@Exchange.Microsoft.com]
Sent: Monday, July 24, 2000 2:06 PM
To: NT Developers Interest List
Subject: [ntdev] Windbg Beta Available

Here is Andre’s mail about the latest debugger release.

<<[windbg] WinDBG BETA>>

A few notes:

To get the list of drivers being loaded during boot you need to
turn
on “verbose” You can do this with the -v command line option.

There is an SDK that can be installed. It contains the new
interfaces that one can use to write more powerful extensions with.
Using
this SDK one can access all functionality of the debugger, which is
implemented in dbgeng.dll. Basicly all Windbg does is gives a UI to
dbgeng.dll. This means that someone could write a replacement debugger
UI &
get all debugger functionality from dbgeng.dll The interfaces are not
in
the documentation yet, so you just have what is in the .h file. Future
releases are planned to have the documentation and samples.

You can turn off Workspace prompting with the -Q command line
option. It answers No to all workspace prompts. The idea is you would
setup your workspace and save it. Then tse the -Q option so you will
always
load the workspace, but never change it.

There are now Save & Clear Workspace items in the File menu.

The UI is now hooked up to pick up the context changes done with
.trap, .thread, .cxr, etc… This means if you do a .thread the call
stack,
locals and other windows will change.

You need to use PDB symbol files to get locals, etc…

Enjoy

Nathan Nesbit
Windows Debugger Team - http://dbg http:

—
You are currently subscribed to ntdev as: xxxxx@exchange.microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)</http:>

4

Hi Nathan.

Please excuse me if this is a simple question. I did a full installation of
the new windbg, and I found the dbgeng.dll, but I was unable to find the
SDK/header file you referred to in your msg below. Could you tell me where
I can these files?

Thanks in advance!

John D. Rogers Mangosoft, Inc. xxxxx@mango.com
mailto:xxxxx

-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@Exchange.Microsoft.com]
Sent: Monday, July 24, 2000 5:06 PM
To: NT Developers Interest List
Subject: [ntdev] Windbg Beta Available

…

There is an SDK that can be installed. It contains the new interfaces that
one can use to write more powerful extensions with. Using this SDK one can
access all functionality of the debugger, which is implemented in
dbgeng.dll. Basicly all Windbg does is gives a UI to dbgeng.dll. This
means that someone could write a replacement debugger UI & get all debugger
functionality from dbgeng.dll The interfaces are not in the documentation
yet, so you just have what is in the .h file. Future releases are planned
to have the documentation and samples.

…</mailto:xxxxx>

5

When you install select Custom Install
When you reach the screen where you can select components, expand the
debugging tools item
You will now see the SDK entry
Click on the SDK entry and a popup menu will appear
Select “Entire Feature will be installed on local hard drive”
Finish the installation

When installation is done there will be a sub dir in the install dir
called SDK.
It has 2 dirs, a inc and lib dir. Everything is in there.

-----Original Message-----
From: John Rogers [mailto:xxxxx@mango.com]
Sent: Monday, July 24, 2000 6:16 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Windbg Beta Available

Hi Nathan.

Please excuse me if this is a simple question. I did a full
installation of
the new windbg, and I found the dbgeng.dll, but I was unable to find the
SDK/header file you referred to in your msg below. Could you tell me
where
I can these files?

Thanks in advance!

John D. Rogers Mangosoft, Inc. xxxxx@mango.com
mailto:xxxxx

-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@Exchange.Microsoft.com]
Sent: Monday, July 24, 2000 5:06 PM
To: NT Developers Interest List
Subject: [ntdev] Windbg Beta Available

…

There is an SDK that can be installed. It contains the new interfaces
that
one can use to write more powerful extensions with. Using this SDK one
can
access all functionality of the debugger, which is implemented in
dbgeng.dll. Basicly all Windbg does is gives a UI to dbgeng.dll. This
means that someone could write a replacement debugger UI & get all
debugger
functionality from dbgeng.dll The interfaces are not in the
documentation
yet, so you just have what is in the .h file. Future releases are
planned
to have the documentation and samples.

…

—
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)</mailto:xxxxx>