Since installing the latest release of WinDbg, I have been encountering
problems and bugs not found in prior releases. Unfortunately, WinDbg’s
stability over the last 7 months has lured me into complacency so when the
system wants to send in a bug report I tell it no thinking that it was a “My
Problem”. I’ll start sending them in.
I have seen at least one instance where attempting to change the
AdapterInterfaceType field in the HW_INITIALIZATION_DATA structure crashed
WinDbg. I had double clicked on the displayed value (PCIBus (5)) and entered
a “F” and WinDbg immediately crashed. I restarted WinDbg, reloaded the
symbols and this time tried a 15, and it appeared to work.
Is this related to my early pissy bitch posting about this release of WinDbg
NOT displaying integer fields in hex? Along that line, I noted that if I
tried to change such a field with something like “C0000001” the change was
refused, but if I used “0xC0000001” then it was accepted, but of course ONLY
displayed it in decimal.
Gary G. Little
Broadband Storage, Inc.
xxxxx@broadstor.com
xxxxx@inland.net
(949) 7372731
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
There were not lots of details about your crash - was this using the memory
window ? What format was the data were you editing ? If you can repro
this and\or get us a dump file of the crash we will definitely get it
fixed. We’ve never seen that problem internally.
As for the editing, that’s by design. The input data can be “overwritten”
and specifying something with 0x indicates the input should be treated as
HEX.
We are adding a command that will force longs to be displayed as HEX
(similar to the command that forces USHORTS to be displayed as unicode
characters).
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Andreva,
I always use WinDbg, and the fault occurred when I attempted to change the
value of a variable in the Locals window. Thus far it was a one time thing.
But then I also haven’t tried what I thought caused the crash. The next time
it happens I will let the wizard send the fault information file.
Gary G. Little
Broadband Storage, Inc.
xxxxx@broadstor.com
xxxxx@inland.net
(949) 7372731
-----Original Message-----
From: xxxxx@microsoft.com [mailto:xxxxx@microsoft.com]
Sent: Saturday, January 05, 2002 4:00 PM
To: Kernel Debugging Interest List
Subject: [windbg] Re: Version 4.00.0018 bugs and problems
There were not lots of details about your crash - was this using the memory
window ? What format was the data were you editing ? If you can repro
this and\or get us a dump file of the crash we will definitely get it
fixed. We’ve never seen that problem internally.
As for the editing, that’s by design. The input data can be “overwritten”
and specifying something with 0x indicates the input should be treated as
HEX.
We are adding a command that will force longs to be displayed as HEX
(similar to the command that forces USHORTS to be displayed as unicode
characters).
You are currently subscribed to windbg as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Andreva.
I have a problem in getting a SCSI pseudo-mini-port attaching to my bus
driver, and I have been stepping through the ScsiPortGlobalDispatch,
ScsiPortFdoPnp, and OS device allocation and release logic trying to figure
out what I need to do to get my find adapter routine called. Needless to say
I spend a lot of time in the disassembly window and register windows reverse
engineering data structures.
WinDbg just crashed twice while I was single stepping through the OS. The XP
wizard popped up and I told it to send the crash report.
Just a note … this instability is new to this release of WinDbg. I have
done much the same with the prior release, with nary a ruffled feather in
WinDbg.
Gary G. Little
Broadband Storage, Inc.
xxxxx@broadstor.com
xxxxx@inland.net
(949) 7372731
-----Original Message-----
From: xxxxx@microsoft.com [mailto:xxxxx@microsoft.com]
Sent: Saturday, January 05, 2002 4:00 PM
To: Kernel Debugging Interest List
Subject: [windbg] Re: Version 4.00.0018 bugs and problems
There were not lots of details about your crash - was this using the memory
window ? What format was the data were you editing ? If you can repro
this and\or get us a dump file of the crash we will definitely get it
fixed. We’ve never seen that problem internally.
As for the editing, that’s by design. The input data can be “overwritten”
and specifying something with 0x indicates the input should be treated as
HEX.
We are adding a command that will force longs to be displayed as HEX
(similar to the command that forces USHORTS to be displayed as unicode
characters).
You are currently subscribed to windbg as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
I’ll vouch for this. I crashed several times when the new version was
first installed and I was stepping through code. If it happens again,
I’ll send the crash report and grab the crash dump. Also it seems that
the known “firewire protocol errors” bug comes up alot more in this
release (though that could just be me doing something different). And
when I try to close WinDBG after getting a firewire protocol error, it
crashes with a memory access violation.
I saw the protocol errors with 4.0.11.0, but didn’t see either of these
crashes in that version…
sean
PS. Any chance the XP Service Pack which fixes the firewire protocol
errors will be out soon? 
Gary Little wrote:
Andreva.
I have a problem in getting a SCSI pseudo-mini-port attaching to my bus
driver, and I have been stepping through the ScsiPortGlobalDispatch,
ScsiPortFdoPnp, and OS device allocation and release logic trying to figure
out what I need to do to get my find adapter routine called. Needless to say
I spend a lot of time in the disassembly window and register windows reverse
engineering data structures.
WinDbg just crashed twice while I was single stepping through the OS. The XP
wizard popped up and I told it to send the crash report.
Just a note … this instability is new to this release of WinDbg. I have
done much the same with the prior release, with nary a ruffled feather in
WinDbg.
Gary G. Little
Broadband Storage, Inc.
xxxxx@broadstor.com
xxxxx@inland.net
(949) 7372731
-----Original Message-----
From: xxxxx@microsoft.com [mailto:xxxxx@microsoft.com]
Sent: Saturday, January 05, 2002 4:00 PM
To: Kernel Debugging Interest List
Subject: [windbg] Re: Version 4.00.0018 bugs and problems
There were not lots of details about your crash - was this using the memory
window ? What format was the data were you editing ? If you can repro
this and\or get us a dump file of the crash we will definitely get it
fixed. We’ve never seen that problem internally.
As for the editing, that’s by design. The input data can be “overwritten”
and specifying something with 0x indicates the input should be treated as
HEX.
We are adding a command that will force longs to be displayed as HEX
(similar to the command that forces USHORTS to be displayed as unicode
characters).
You are currently subscribed to windbg as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: xxxxx@stg.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Each time you see a crash, please click the submit button. We really need
the bug reports in order for us to fix the bugs.
We had zero known crashing bugs when we released. If we can identify these
crashes, we’ll get them fixed as quickly as possible.
SP1 will have greatly improved 1394 debugging support, that eliminates all
these protocol errors.
-Andre
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com