WinDbg gets confused about source locations?

WINDBG
1

Hi folks,

Seen a rather irritating little quirk of WinDbg. Sometimes, when I’m testing a
driver, I’ll want to compare the behaviour of my current version and an earlier
version. The drivers have the same name, but of course are built from source
paths on different drives. However, sometimes, WinDbg appears to get rather
confused about which one it’s currently looking at… to the point where
“.reload” and “.reload /f” are not sufficient to convince it that it needs to
update its ideas.

Any suggestions on how to deal with this?

MH.

This email and any attachments is confidential, may be legally privileged and is intended for the use of the addressee only. If you are not the intended recipient, please note that any use, disclosure, printing or copying of this email is strictly prohibited and may be unlawful. If received in error, please delete this email and any attachments and confirm this to the sender.

2

.reload does not affect source code loading. You should do “Close all
source”, then change your source path. After that, reopening your
source files should get the correct version.

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@snellwilcox.com
Sent: Tuesday, November 09, 2004 2:37 AM
To: Kernel Debugging Interest List
Subject: [windbg] WinDbg gets confused about source locations?

Hi folks,

Seen a rather irritating little quirk of WinDbg. Sometimes, when I’m
testing a
driver, I’ll want to compare the behaviour of my current version and an
earlier
version. The drivers have the same name, but of course are built from
source
paths on different drives. However, sometimes, WinDbg appears to get
rather
confused about which one it’s currently looking at… to the point where
“.reload” and “.reload /f” are not sufficient to convince it that it
needs to
update its ideas.

Any suggestions on how to deal with this?

MH.

This email and any attachments is confidential, may be legally
privileged and is intended for the use of the addressee only. If you are
not the intended recipient, please note that any use, disclosure,
printing or copying of this email is strictly prohibited and may be
unlawful. If received in error, please delete this email and any
attachments and confirm this to the sender.

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