Thanks … That explanation is not in the documentation, so I kinda
scratched my … uh … head … when I encountered it.
The strange thing is that I have two versions of the driver for two
different boards but sharing common code. One copies but the other does
not, with this warning.
Gary G. Little
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Tuesday, February 07, 2006 1:37 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Command I’ve forgotten
That means that the target requested a remote file open but did not do
any I/O. It means that .kdfiles is active but not having any effect.
There’s no way for kd to know exactly why not, it can only warn that no
I/O was done.
The usual cause for this is that something interfered with the copying
on the target side, such as an antivirus or protection product
preventing access to the driver file on the target.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, February 07, 2006 11:29 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Command I’ve forgotten
Drew,
When using .kdfiles to map to a newer version of a driver, what does
“WARNING: No file I/O done by target, .kdfiles files may not be updated”
mean? I’ve rebuilt the driver and want it to load, but it does not when
this message is displayed. How do I correct the problem that this
message warns me about?
Gary G. Little
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jonathan Ludwig
Sent: Tuesday, February 07, 2006 1:10 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Command I’ve forgotten
No, after opening a crash dump I’ve entered a command before that pulled
debug output from a buffer in the dump file (some output buffer in
memory somewhere). Some times it will spit out a few lines of output
that would have gone to the command window had it been flushed to a
debugger.
wrote in message news:xxxxx@windbg…
> Are you referring to File->Open Crash Dump (Ctl+D), or “opendump”?
>
> Gary G. Little
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Jonathan
> Ludwig
> Sent: Tuesday, February 07, 2006 12:59 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] Command I’v forgotten
>
> I’ve forgotten a debugger command I haven’t use in a while. There is
> a command to pull debug output out of a dump file from the debug
buffer.
I
> can’t remember what it is. For some reason I can’t seem to find it in
the
>
> help either. Can some one remind me what the command is?
>
> Thanks,
>
> Jonathan
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@seagate.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
—
You are currently subscribed to windbg as: xxxxx@seagate.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com