fasmotol
February 27th, 2013, 14:17
Hi, woodmann!
Few days ago while i was launching bundle of vmware + vmmon + windbg smth went (or i typed smth) wrong and now windbg is loading symbols for every module! I mean before @lm@ command showed me alot of (deferred) fields: symbols were loaded in runtime only when windbg (or me) needed them. But now it's looking for symbols for every_one_module. That just grinds my gear, cus booting vm with debugger connected takes >10m!
I tried to play around with symbols flags (.symopt), but achieved nothing. For now that's my set:
Can someone tellme their own set? Perhaps there are some additional flags in registry affecting way symbols are loaded etc.
Few days ago while i was launching bundle of vmware + vmmon + windbg smth went (or i typed smth) wrong and now windbg is loading symbols for every module! I mean before @lm@ command showed me alot of (deferred) fields: symbols were loaded in runtime only when windbg (or me) needed them. But now it's looking for symbols for every_one_module. That just grinds my gear, cus booting vm with debugger connected takes >10m!
I tried to play around with symbols flags (.symopt), but achieved nothing. For now that's my set:
Code:
0: kd> .symopt
Symbol options are 0x30237:
0x00000001 - SYMOPT_CASE_INSENSITIVE
0x00000002 - SYMOPT_UNDNAME
0x00000004 - SYMOPT_DEFERRED_LOADS
0x00000010 - SYMOPT_LOAD_LINES
0x00000020 - SYMOPT_OMAP_FIND_NEAREST
0x00000200 - SYMOPT_FAIL_CRITICAL_ERRORS
0x00010000 - SYMOPT_AUTO_PUBLICS
0x00020000 - SYMOPT_NO_IMAGE_SEARCH
Can someone tellme their own set? Perhaps there are some additional flags in registry affecting way symbols are loaded etc.