“Andre Vachon” wrote in message
news:<#xxxxx@tkmsftngp05>…
> WinDBG 2.0 was released to the web on Feb. 15th 2001.
> This new version of WinDBG contains numerous enhancements over the 1.0
> WinDBG release from Sept. 2000. New features include:
>
> * Support for the new Visual Studio.Net PDB format
> * Enhancements to the dt and .dump commands
> * Many command enhancements such as .process, kp, etc
> * Workspace enhancements for saving the window title, default source
path,
> kernel debugging settings, etc
> * Enhanced user-mode dump file format: added handle table,
user-defined
> comments, timestamp the dump file was created
> * Many new “sx” events (including initial module load and initial
> breakpoint); now all events can have associated commands
> * Physical memory cache for faster kernel debugging performance
> * More complete disassembler
> * More documentation, including how to debug over a 1394 port
>
> This new version of WinDBG is also more reliable than any past
version, and
> we encourage ALL developers debugging code on NT platforms (NT4,
Windows
> 2000, Windows Whistler) to update to this new version.
>
> You can download this latest version of the debuggers from
> http://www.microsoft.com/ddk/debugging
> The debugger download contains the debuggers, debugger extensions,
> documentation and a few other debugging tools.
>
> To report bugs or issues, or submit request for new features, please
send
> mail to xxxxx@microsoft.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
Irritating problem:
When setting a breakpoint such as “bp StartPacket”, I get a stream of
complaints about bad time stamps on sys files. The bp is set and triggers
properly, but the complaints about timestamps on files that I know are valid
(they are the 2000 SP1 pdb files) is irritating. and time consuming.
Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@Exchange.Microsoft.com]
Sent: Tuesday, February 20, 2001 10:34 AM
To: NT Developers Interest List
Subject: [ntdev] Fw: windbg 2.0 release
“Andre Vachon” wrote in message
news:<#xxxxx@tkmsftngp05>…
> WinDBG 2.0 was released to the web on Feb. 15th 2001.
> This new version of WinDBG contains numerous enhancements over the 1.0
> WinDBG release from Sept. 2000. New features include:
>
> * Support for the new Visual Studio.Net PDB format
> * Enhancements to the dt and .dump commands
> * Many command enhancements such as .process, kp, etc
> * Workspace enhancements for saving the window title, default source
path,
> kernel debugging settings, etc
> * Enhanced user-mode dump file format: added handle table,
user-defined
> comments, timestamp the dump file was created
> * Many new “sx” events (including initial module load and initial
> breakpoint); now all events can have associated commands
> * Physical memory cache for faster kernel debugging performance
> * More complete disassembler
> * More documentation, including how to debug over a 1394 port
>
> This new version of WinDBG is also more reliable than any past
version, and
> we encourage ALL developers debugging code on NT platforms (NT4,
Windows
> 2000, Windows Whistler) to update to this new version.
>
> You can download this latest version of the debuggers from
> http://www.microsoft.com/ddk/debugging
> The debugger download contains the debuggers, debugger extensions,
> documentation and a few other debugging tools.
>
> To report bugs or issues, or submit request for new features, please
send
> mail to xxxxx@microsoft.com
>
>
>
>
—
You are currently subscribed to ntdev as: xxxxx@delphieng.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
Try bp “mydriver!StartPacket”, where mydriver is the name of your driver.
Does that fix it?
Phil
-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Tuesday, February 20, 2001 12:06 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Fw: windbg 2.0 release
Irritating problem:
When setting a breakpoint such as “bp StartPacket”, I get a stream of
complaints about bad time stamps on sys files. The bp is set and triggers
properly, but the complaints about timestamps on files that I know are valid
(they are the 2000 SP1 pdb files) is irritating. and time consuming.
Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@Exchange.Microsoft.com]
Sent: Tuesday, February 20, 2001 10:34 AM
To: NT Developers Interest List
Subject: [ntdev] Fw: windbg 2.0 release
“Andre Vachon” wrote in message
news:<#xxxxx@tkmsftngp05>…
> WinDBG 2.0 was released to the web on Feb. 15th 2001.
> This new version of WinDBG contains numerous enhancements over the 1.0
> WinDBG release from Sept. 2000. New features include:
>
> * Support for the new Visual Studio.Net PDB format
> * Enhancements to the dt and .dump commands
> * Many command enhancements such as .process, kp, etc
> * Workspace enhancements for saving the window title, default source
path,
> kernel debugging settings, etc
> * Enhanced user-mode dump file format: added handle table,
user-defined
> comments, timestamp the dump file was created
> * Many new “sx” events (including initial module load and initial
> breakpoint); now all events can have associated commands
> * Physical memory cache for faster kernel debugging performance
> * More complete disassembler
> * More documentation, including how to debug over a 1394 port
>
> This new version of WinDBG is also more reliable than any past
version, and
> we encourage ALL developers debugging code on NT platforms (NT4,
Windows
> 2000, Windows Whistler) to update to this new version.
>
> You can download this latest version of the debuggers from
> http://www.microsoft.com/ddk/debugging
> The debugger download contains the debuggers, debugger extensions,
> documentation and a few other debugging tools.
>
> To report bugs or issues, or submit request for new features, please
send
> mail to xxxxx@microsoft.com
>
>
>
>
—
You are currently subscribed to ntdev as: xxxxx@delphieng.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@intel.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
“WARNING: Unable to verify Timestamp for fgpeer.sys” is the only message
that returns. All that does is specify the module. “bp StartPacket” still
returns errors on all sys files.
I’m using VC++ 6.0, Enterprise edition, and directly copying the pdb file to
the symbols path.
Again, this was not seen in the winDbg 2.0 beta. Please don’t tell me this
version of winDbg expects 7.0 symbologies.
Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com
-----Original Message-----
From: Barila, Phil [mailto:xxxxx@intel.com]
Sent: Tuesday, February 20, 2001 12:47 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Fw: windbg 2.0 release
Try bp “mydriver!StartPacket”, where mydriver is the name of your driver.
Does that fix it?
Phil
-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Tuesday, February 20, 2001 12:06 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Fw: windbg 2.0 release
Irritating problem:
When setting a breakpoint such as “bp StartPacket”, I get a stream of
complaints about bad time stamps on sys files. The bp is set and triggers
properly, but the complaints about timestamps on files that I know are valid
(they are the 2000 SP1 pdb files) is irritating. and time consuming.
Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com
-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@Exchange.Microsoft.com]
Sent: Tuesday, February 20, 2001 10:34 AM
To: NT Developers Interest List
Subject: [ntdev] Fw: windbg 2.0 release
“Andre Vachon” wrote in message
news:<#xxxxx@tkmsftngp05>…
> WinDBG 2.0 was released to the web on Feb. 15th 2001.
> This new version of WinDBG contains numerous enhancements over the 1.0
> WinDBG release from Sept. 2000. New features include:
>
> * Support for the new Visual Studio.Net PDB format
> * Enhancements to the dt and .dump commands
> * Many command enhancements such as .process, kp, etc
> * Workspace enhancements for saving the window title, default source
path,
> kernel debugging settings, etc
> * Enhanced user-mode dump file format: added handle table,
user-defined
> comments, timestamp the dump file was created
> * Many new “sx” events (including initial module load and initial
> breakpoint); now all events can have associated commands
> * Physical memory cache for faster kernel debugging performance
> * More complete disassembler
> * More documentation, including how to debug over a 1394 port
>
> This new version of WinDBG is also more reliable than any past
version, and
> we encourage ALL developers debugging code on NT platforms (NT4,
Windows
> 2000, Windows Whistler) to update to this new version.
>
> You can download this latest version of the debuggers from
> http://www.microsoft.com/ddk/debugging
> The debugger download contains the debuggers, debugger extensions,
> documentation and a few other debugging tools.
>
> To report bugs or issues, or submit request for new features, please
send
> mail to xxxxx@microsoft.com
>
>
>
>
—
You are currently subscribed to ntdev as: xxxxx@delphieng.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@delphieng.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
“.reload” should clear all that up.
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
My apologies. I hadn’t actually lit up the new one. I get the same
annoying message, for every module for which the 'bag loads symbols.
Phil
-----Original Message-----
From: Gary Little [mailto:xxxxx@Broadstor.com]
Sent: Tuesday, February 20, 2001 2:56 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Fw: windbg 2.0 release
“WARNING: Unable to verify Timestamp for fgpeer.sys” is the only message
that returns. All that does is specify the module. “bp StartPacket” still
returns errors on all sys files.
I’m using VC++ 6.0, Enterprise edition, and directly copying the pdb file to
the symbols path.
Again, this was not seen in the winDbg 2.0 beta. Please don’t tell me this
version of winDbg expects 7.0 symbologies.
Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.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
Yes, !reload resolves the complaint about symbol timestamps. But why is it
needed? Your telling me that ver. 2.0 does not now load symbols as the
target boots? When using the beta, the only time I saw complaints about
symbol files is when I would switch from NT4 to 2000 or XP and I did not
have the symbol paths set correctly for the particular environment that I
was now in.
Has 2.0 been “dumbed-down”?
Honestly, there is a lot of things to like in 2.0. But for me, this one is a
pain in the ass. It’s something else I have to remember to do, and it takes
a long time to do, when I’ve only got 3 or 4 seconds before an interrupt is
going to trigger and screw my test.
Gary G. Little
Sr. Staff Engineer
Broadband Storage, LLC
xxxxx@broadstor.com
xxxxx@delphieng.com
-----Original Message-----
From: xxxxx@microsoft.com [mailto:xxxxx@microsoft.com]
Sent: Tuesday, February 20, 2001 4:00 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Fw: windbg 2.0 release
“.reload” should clear all that up.
You are currently subscribed to ntdev as: xxxxx@delphieng.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