Discussion:
symbol and image file locations
(too old to reply)
Chris Becke
2007-09-14 14:21:52 UTC
Permalink
One of the scripts in our build process uploads to a symbol server on a UNC
path.

Ive had some success configuring windbg to use the symbol server, but parts
of the process work on and off...

I have configured the symbol file search path to the following two lines...

SRV*e:\symstore*http://msdl.microsoft.com/download/symbols
SRV*e:\symstore*\\build\symstore

The first line references the microsoft symbol server so I can get symbols
for kernel32.dll etc. The second line references the location on our build
server.

My problems are - when loading mini crash dumps....
If the crash happens on a PC with a different OS, windbg will get the
correct pdb files, but sometimes it wont get the system dll.

Adding the lines from "Symbol File Path..." to the "Image File Path..."
seems to resolve this.

My own projects dlls dont always seem to resolve, I want to get binaries
locally to my own machine always so in future debug attempts there is no
delay, so I'm using the SRV*local*remote syntax. Is this expected to work
when listed multiple times and should I list each path on its own line, or
use some other seperator?
Pat Styles [MSFT]
2007-09-14 22:44:05 UTC
Permalink
Hello Chris.

Symbol paths are not to be listed on separate lines. You should use the
semicolon as a separator between two different elements of the symbol path.
And if you want to use a local store, you should specify it in each element
of the symbol path. Look in future versions of the debugger for the
"cache*" feature.

srv*e:\symstore*\\build\symstore;srv*e:\symstore*http://msdl.microsoft.com/download/symbols

.pat styles [msft]


"Chris Becke" <***@gmail.com> wrote in message news:***@TK2MSFTNGP05.phx.gbl...
One of the scripts in our build process uploads to a symbol server on a UNC
path.

Ive had some success configuring windbg to use the symbol server, but parts
of the process work on and off...

I have configured the symbol file search path to the following two lines...

SRV*e:\symstore*http://msdl.microsoft.com/download/symbols
SRV*e:\symstore*\\build\symstore

The first line references the microsoft symbol server so I can get symbols
for kernel32.dll etc. The second line references the location on our build
server.

My problems are - when loading mini crash dumps....
If the crash happens on a PC with a different OS, windbg will get the
correct pdb files, but sometimes it wont get the system dll.

Adding the lines from "Symbol File Path..." to the "Image File Path..."
seems to resolve this.

My own projects dlls dont always seem to resolve, I want to get binaries
locally to my own machine always so in future debug attempts there is no
delay, so I'm using the SRV*local*remote syntax. Is this expected to work
when listed multiple times and should I list each path on its own line, or
use some other seperator?
David J. Craig
2007-09-14 23:31:29 UTC
Permalink
I would recommend that you keep the two local stores in different
directories. It just makes it easier to cleanup old versions of your
symbols as most developers may have many different versions, most of which
are no longer available. Then you can just delete the entire directory to
recover disk space. If you have a symbol server for your products, then it
can get the ones saved easily and quickly.

Also always put the local symbol server first since it should have the
fastest access.
Post by Pat Styles [MSFT]
Hello Chris.
Symbol paths are not to be listed on separate lines. You should use the
semicolon as a separator between two different elements of the symbol path.
And if you want to use a local store, you should specify it in each element
of the symbol path. Look in future versions of the debugger for the
"cache*" feature.
srv*e:\symstore*\\build\symstore;srv*e:\symstore*http://msdl.microsoft.com/download/symbols
.pat styles [msft]
One of the scripts in our build process uploads to a symbol server on a UNC
path.
Ive had some success configuring windbg to use the symbol server, but parts
of the process work on and off...
I have configured the symbol file search path to the following two lines...
SRV*e:\symstore*http://msdl.microsoft.com/download/symbols
SRV*e:\symstore*\\build\symstore
The first line references the microsoft symbol server so I can get symbols
for kernel32.dll etc. The second line references the location on our build
server.
My problems are - when loading mini crash dumps....
If the crash happens on a PC with a different OS, windbg will get the
correct pdb files, but sometimes it wont get the system dll.
Adding the lines from "Symbol File Path..." to the "Image File Path..."
seems to resolve this.
My own projects dlls dont always seem to resolve, I want to get binaries
locally to my own machine always so in future debug attempts there is no
delay, so I'm using the SRV*local*remote syntax. Is this expected to work
when listed multiple times and should I list each path on its own line, or
use some other seperator?
Loading...