Newbie Question on Symbols

When I first fired up WinDbg (3.0.20.0), I had symbols on my host machines
drive (C:\somepath\mydriver.pdb). Fine, great, no problem, they loaded.

However, because my development machine and host/target machines are in
different rooms, I’m trying to get the symbols to load from
\[networkpath]\mydriver.pdb. The problem is that no matter what changes I
make in the File=>Symbol Path… dialogs, WinDbg insists on loading the
symbols from C:\somepath\mydriver.pdb (I checked using the LM command).

Any suggestions?

Thanks,


You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

try
!sym noisy
.reload

-----Original Message-----
From: xxxxx@troikanetworks.com
[mailto:xxxxx@troikanetworks.com]
Sent: Monday, July 30, 2001 7:55 AM
To: Kernel Debugging Interest List
Subject: [windbg] Newbie Question on Symbols

When I first fired up WinDbg (3.0.20.0), I had symbols on my host machines
drive (C:\somepath\mydriver.pdb). Fine, great, no problem, they loaded.

However, because my development machine and host/target machines are in
different rooms, I’m trying to get the symbols to load from
\[networkpath]\mydriver.pdb. The problem is that no matter what changes I
make in the File=>Symbol Path… dialogs, WinDbg insists on loading the
symbols from C:\somepath\mydriver.pdb (I checked using the LM command).

Any suggestions?

Thanks,


You are currently subscribed to windbg as: xxxxx@ncr.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

I hope that Venu’s help was useful to you. Just so you know the
debugger attempts to load symbols from many places. Here they are (in
no particular order)

  1. From the current directory
  2. From the directory the binary is in
  3. From each element in the sympath
  4. From the hardcoded path in the binary

As Venu pointed out turning on noisy symbol loading (with “!sym noisy”
or -n on the command line) will help you discover where the debugger is
looking for symbols and more verbose information on any errors it finds.

Hopefully this has already solved your problem.

-----Original Message-----
From: Joshi, Venu [mailto:xxxxx@exchange.SanDiegoCA.NCR.COM]
Sent: Monday, July 30, 2001 12:10 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Newbie Question on Symbols

try
!sym noisy
.reload

-----Original Message-----
From: xxxxx@troikanetworks.com
[mailto:xxxxx@troikanetworks.com]
Sent: Monday, July 30, 2001 7:55 AM
To: Kernel Debugging Interest List
Subject: [windbg] Newbie Question on Symbols

When I first fired up WinDbg (3.0.20.0), I had symbols on my host
machines
drive (C:\somepath\mydriver.pdb). Fine, great, no problem, they loaded.

However, because my development machine and host/target machines are in
different rooms, I’m trying to get the symbols to load from
\[networkpath]\mydriver.pdb. The problem is that no matter what
changes I
make in the File=>Symbol Path… dialogs, WinDbg insists on loading the
symbols from C:\somepath\mydriver.pdb (I checked using the LM command).

Any suggestions?

Thanks,


You are currently subscribed to windbg as: xxxxx@ncr.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

try mapping a network drive (giving it a letter)
and loading the symbols from there. It seems
more reliable, so that you load
!load q:\xdir\foo.dll where you’ve mapped
q to your network location.

for some reason windbg seems to like it better.
sometimes it seems I even have to go into explorer
and ‘refresh’ the connection (by browsing the
drive). That may be an artifact of our network.


You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

There shouldn’t be any problem loading symbols or extensions from UNC
paths. Thousands of people in the windows group do it everyday. All
the debugger really does is pass these paths to various Win32 APIs.

Sounds from your description that something independent of the debugger
is wrong with your network.

-----Original Message-----
From: xxxxx@starband.net [mailto:xxxxx@starband.net]
Sent: Friday, August 03, 2001 2:20 AM
To: Kernel Debugging Interest List
Subject: [windbg] Re: Newbie Question on Symbols

try mapping a network drive (giving it a letter)
and loading the symbols from there. It seems
more reliable, so that you load
!load q:\xdir\foo.dll where you’ve mapped
q to your network location.

for some reason windbg seems to like it better.
sometimes it seems I even have to go into explorer
and ‘refresh’ the connection (by browsing the
drive). That may be an artifact of our network.


You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com