visual studio debugging - Why is VS 2010 ignoring _NT_SYMBOL_PATH? -
does vs 2010 handle symbol file resolution differently other ms products? repro steps:
- open control panel , make sure _nt_symbol_path set valid, srv*c:\debugsymbols*\buildserver\builds\symbols*http://msdl.microsoft.com/download/symbols
- open minidump file windbg or vs 2012 => debugger succeeds loading symbols
- open same minidump file vs 2010 => debugger fails find symbols
- open options dialog inside vs , set debugging symbols path same 1 above. (this setting saved when close vs.)
- open same minidump file vs 2010 => debugger succeeds loading symbols
this repro's on machines in our dept. setting path manually one-time operation , it's fine on dev box, it's major pain in lab vms reimaged.
does 2010 use additional environment variable(s) other tools don't?
does vs have master settings file, overridden each user's currentsettings.vssettings?
after asking around , scouring web, found out reliable source
_nt_symbol_path environment variable consumed same component vs uses load symbols, not used vs.
i believe comment specific vs 2010 (unconfirmed). unable reproduce issue in vs 2012.
it's related more common issue vs ignore local cache, causing performance problems, though it's set in _nt_symbol_path.
the workaround set path manually inside vs 2010, or (better yet) open crash dump in vs 2012.
Comments
Post a Comment