On Vista RC1, I am getting lots of output like this when using !irpfind:
VirtualToOffset: 97ce6000 not properly sign extended
Is there anyway to suppress this message?
There isn’t any way to suppress it. It indicates a problem in the
extension, so the extension would need to be fixed. I’ll ask if this is
known.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Takin
Nili-Esfahani
Sent: Monday, October 09, 2006 7:37 PM
To: Kernel Debugging Interest List
Subject: [windbg] Trouble with !irpfind
On Vista RC1, I am getting lots of output like this when using !irpfind:
VirtualToOffset: 97ce6000 not properly sign extended
Is there anyway to suppress this message?
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
While you’ve clearly indicated that the debugger team does not own the
extensions (which are what makes the debugger useful to many of us) I am
curious who signs off on including them in the debugger package for each
release. Absent any sort of testing paradigm it seems that they will
“bit rot” over time and become broken.
As for the error messages, unfortunately they are being sent to the
wrong people. It’d be FAR better if each one of these generated an
e-mail to the manager of the dev responsible for the extension (I bet
it’d get fixed a LOT faster that way!) Reporting it to the poor user is
essentially useless, since they have no idea what it means and they have
no way of fixing it.
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
There isn’t any way to suppress it [the error messages]. It indicates
a problem in the
extension, so the extension would need to be fixed. I’ll ask if this
is
known.
There isn’t a formal sign-off process for extensions. The thinking is
that if people can use them and get some value that’s better than not
shipping them at all, even if that means we’re sending out code which
isn’t necessarily going to work 100%.
I asked about ownership of !irpfind and it’s fairly vague. If somebody
has a simple repro case of the sign extension problem that we can run
here at Microsoft we can investigate further.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Monday, October 09, 2006 8:28 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Trouble with !irpfind
While you’ve clearly indicated that the debugger team does not own the
extensions (which are what makes the debugger useful to many of us) I am
curious who signs off on including them in the debugger package for each
release. Absent any sort of testing paradigm it seems that they will
“bit rot” over time and become broken.
As for the error messages, unfortunately they are being sent to the
wrong people. It’d be FAR better if each one of these generated an
e-mail to the manager of the dev responsible for the extension (I bet
it’d get fixed a LOT faster that way!) Reporting it to the poor user is
essentially useless, since they have no idea what it means and they have
no way of fixing it.
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
There isn’t any way to suppress it [the error messages]. It indicates
a problem in the
extension, so the extension would need to be fixed. I’ll ask if this
is
known.
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com