Debugging, sometimes source shows sometimes it doesn't

WINDBG
1

Hello

2

Hello

I wrote a small driver and build for W2k checked.

Using WinXP (in debug mode) in VPC2004, WinDbg manages to attach to the
system and debug it.

After copying the .sys file to the guest machine, sometimes WinDbg shows the
source code and sometimes it just debugs my driver in ASM mode!

The .sys file, has correct information pointing to the location of .pdb in
the host machine.

I am using WinDbg 6.6.0003.5

Please tell me how to assure that WinDbg will always debug my driver in
source code mode?

–
Elias

3

When that happens to me, I have found it is a sync issue between the SYS,
PDB, and sources files. In other words, you did not update your SYS file
after a build, and as a consequence, the binary, PDB, and sources files do
not resolve to meaningful locations in the source, so WinDbg defaults to
assembly as a last ditch effort to let you do something.

You said you copied the SYS file, but did you disable/enable the driver or
uninstall/install it using Device Manager on the machine running the
driver? When in doubt, boot the target.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of lallous
Sent: Tuesday, May 02, 2006 8:07 AM
To: Kernel Debugging Interest List
Subject: [windbg] Debugging, sometimes source shows sometimes it doesn’t

Hello

I wrote a small driver and build for W2k checked.

Using WinXP (in debug mode) in VPC2004, WinDbg manages to attach to the
system and debug it.

After copying the .sys file to the guest machine, sometimes WinDbg shows
the
source code and sometimes it just debugs my driver in ASM mode!

The .sys file, has correct information pointing to the location of .pdb in

the host machine.

I am using WinDbg 6.6.0003.5

Please tell me how to assure that WinDbg will always debug my driver in
source code mode?

–
Elias

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

4

To add on, you should check:

  1. Ensure symbols are loading for your driver.
  2. Ensure you have private symbols (listed as such in lm).
  3. Enable line loading (done automatically by windbg, but do .lines -e
    to be sure).
  4. See if you have source line info. Do l+l and then ln
    yourdriver!somesymbolinyourdriver and see if source line info is
    displayed.
  5. Check your source path and make sure source is accessible through it.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Tuesday, May 02, 2006 7:29 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Debugging, sometimes source shows sometimes it
doesn’t

When that happens to me, I have found it is a sync issue between the
SYS, PDB, and sources files. In other words, you did not update your SYS
file after a build, and as a consequence, the binary, PDB, and sources
files do not resolve to meaningful locations in the source, so WinDbg
defaults to assembly as a last ditch effort to let you do something.

You said you copied the SYS file, but did you disable/enable the driver
or uninstall/install it using Device Manager on the machine running the
driver? When in doubt, boot the target.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of lallous
Sent: Tuesday, May 02, 2006 8:07 AM
To: Kernel Debugging Interest List
Subject: [windbg] Debugging, sometimes source shows sometimes it doesn’t

Hello

I wrote a small driver and build for W2k checked.

Using WinXP (in debug mode) in VPC2004, WinDbg manages to attach to the
system and debug it.

After copying the .sys file to the guest machine, sometimes WinDbg shows
the source code and sometimes it just debugs my driver in ASM mode!

The .sys file, has correct information pointing to the location of .pdb
in

the host machine.

I am using WinDbg 6.6.0003.5

Please tell me how to assure that WinDbg will always debug my driver in
source code mode?

–
Elias

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

5

I concur.

>> xxxxx@seagate.com 2006-05-02 10:28 >>>
When that happens to me, I have found it is a sync issue between the
SYS,
PDB, and sources files. In other words, you did not update your SYS
file
after a build, and as a consequence, the binary, PDB, and sources files
do
not resolve to meaningful locations in the source, so WinDbg defaults
to
assembly as a last ditch effort to let you do something.

You said you copied the SYS file, but did you disable/enable the driver
or
uninstall/install it using Device Manager on the machine running the
driver? When in doubt, boot the target.

Gary G. Little

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of lallous
Sent: Tuesday, May 02, 2006 8:07 AM
To: Kernel Debugging Interest List
Subject: [windbg] Debugging, sometimes source shows sometimes it
doesn’t

Hello

I wrote a small driver and build for W2k checked.

Using WinXP (in debug mode) in VPC2004, WinDbg manages to attach to the

system and debug it.

After copying the .sys file to the guest machine, sometimes WinDbg
shows
the
source code and sometimes it just debugs my driver in ASM mode!

The .sys file, has correct information pointing to the location of .pdb
in

the host machine.

I am using WinDbg 6.6.0003.5

Please tell me how to assure that WinDbg will always debug my driver in

source code mode?

–
Elias

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@evitechnology.com
To unsubscribe send a blank email to xxxxx@lists.osr.com