No output from lm

This is one particular system that when I connect to it via a com port, lm
just shows:
kd> lm
start end module name
804d4000 806c6980 nt (pdb symbols)
c:\Symbols\ntoskrnl.pdb\C95EC79CFBFB4220AF2B6E9D09551A1F2\ntoskrnl.pdb

Unloaded modules:
f8728000 f8732000 imapi.sys
f86e8000 f86f8000 serial.sys
f8830000 f8835000 Cdaudio.SYS
f8a30000 f8a33000 Sfloppy.SYS
f8a3c000 f8a3e000 intelide.sys

Now, I know my driver is loaded, because I can see output from it, and of
course there are other driver that are loaded.
Any idea what causes this?

Your loaded module list isn’t properly populated. This usually happens if
you connect WinDBG to a system after it has already booted since WinDBG
wasn’t there to be notified of the image load events. You get the same
behavior when opening a local kernel debug session.

Force a symbol reload (.reload) and all should be well.

-scott


Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Jim Donelson” wrote in message news:xxxxx@windbg…

This is one particular system that when I connect to it via a com port, lm
just shows:
kd> lm
start end module name
804d4000 806c6980 nt (pdb symbols)
c:\Symbols\ntoskrnl.pdb\C95EC79CFBFB4220AF2B6E9D09551A1F2\ntoskrnl.pdb

Unloaded modules:
f8728000 f8732000 imapi.sys
f86e8000 f86f8000 serial.sys
f8830000 f8835000 Cdaudio.SYS
f8a30000 f8a33000 Sfloppy.SYS
f8a3c000 f8a3e000 intelide.sys

Now, I know my driver is loaded, because I can see output from it, and of
course there are other driver that are loaded.
Any idea what causes this?

Well, I did reload, and I also connected at reboot.
Still nothing.
Here is the odd thing, if I put a break point for mydriver!DriverEntry and
reboot (it’s a boot driver that can not unload) , I hit it - then symbols
load etc.
I can then set other break points.
Now, of course, that the test conditions are gone, lm works fine (I normally
can just connect, set the symbol path,. reload and set a break point).

Oh well, life with the bag.
Thanks…

On Fri, Nov 21, 2008 at 2:30 PM, Scott Noone wrote:

> Your loaded module list isn’t properly populated. This usually happens if
> you connect WinDBG to a system after it has already booted since WinDBG
> wasn’t there to be notified of the image load events. You get the same
> behavior when opening a local kernel debug session.
>
> Force a symbol reload (.reload) and all should be well.
>
> -scott
>
>
> –
> Scott Noone
> Software Engineer
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
>
>
> “Jim Donelson” wrote in message news:xxxxx@windbg…
>
> This is one particular system that when I connect to it via a com port, lm
> just shows:
> kd> lm
> start end module name
> 804d4000 806c6980 nt (pdb symbols)
> c:\Symbols\ntoskrnl.pdb\C95EC79CFBFB4220AF2B6E9D09551A1F2\ntoskrnl.pdb
>
> Unloaded modules:
> f8728000 f8732000 imapi.sys
> f86e8000 f86f8000 serial.sys
> f8830000 f8835000 Cdaudio.SYS
> f8a30000 f8a33000 Sfloppy.SYS
> f8a3c000 f8a3e000 intelide.sys
>
> Now, I know my driver is loaded, because I can see output from it, and of
> course there are other driver that are loaded.
> Any idea what causes this?
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@jimdonelson.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

Weird. I see it all the time in Debug Lab and the .reload usually fixes it.

God grant me the serenity…

-scott


Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Jim Donelson” wrote in message news:xxxxx@windbg…
Well, I did reload, and I also connected at reboot.
Still nothing.
Here is the odd thing, if I put a break point for mydriver!DriverEntry and
reboot (it’s a boot driver that can not unload) , I hit it - then symbols
load etc.
I can then set other break points.
Now, of course, that the test conditions are gone, lm works fine (I normally
can just connect, set the symbol path,. reload and set a break point).

Oh well, life with the bag.
Thanks…

On Fri, Nov 21, 2008 at 2:30 PM, Scott Noone wrote:

Your loaded module list isn’t properly populated. This usually happens if
you connect WinDBG to a system after it has already booted since WinDBG
wasn’t there to be notified of the image load events. You get the same
behavior when opening a local kernel debug session.

Force a symbol reload (.reload) and all should be well.

-scott


Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Jim Donelson” wrote in message news:xxxxx@windbg…

This is one particular system that when I connect to it via a com port, lm
just shows:
kd> lm
start end module name
804d4000 806c6980 nt (pdb symbols)
c:\Symbols\ntoskrnl.pdb\C95EC79CFBFB4220AF2B6E9D09551A1F2\ntoskrnl.pdb

Unloaded modules:
f8728000 f8732000 imapi.sys
f86e8000 f86f8000 serial.sys
f8830000 f8835000 Cdaudio.SYS
f8a30000 f8a33000 Sfloppy.SYS
f8a3c000 f8a3e000 intelide.sys

Now, I know my driver is loaded, because I can see output from it, and of
course there are other driver that are loaded.
Any idea what causes this?


You are currently subscribed to windbg as: xxxxx@jimdonelson.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Hello Jim,

* On Fri, Nov 21, 2008 at 03:49:26PM -0500 Jim Donelson wrote:

Well, I did reload, and I also connected at reboot.
Still nothing.

I have seen this behaviour with older versions of WinDBG. However, I
don’t think I have seen this the last 3 years or so.

I don’t know how and why this problem is triggered, and I don’t know if
it was fixed, or if something changed on my side.

For me, when this happened, both the debugger and the debuggee ran XP.

Regards,
Spiro.


Spiro R. Trikaliotis http://opencbm.sf.net/
http://www.trikaliotis.net/ http://www.viceteam.org/