PDA

View Full Version : WinDbg: let's load em all!


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:
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.

Extremist
February 27th, 2013, 16:12
.symopt+0x100

SYMOPT_NO_UNQUALIFIED_LOADS

blabberer
February 27th, 2013, 17:16
there might be an unresolved breakpoint
bu somemodule!SomeFunction
and windbg might be trying to resolve it and load all symbols in the process

try clearing bps / clearing workspaces etc

fasmotol
February 28th, 2013, 01:56
Wow, thanks, Extremist!
blabberer, i don't think it's the issue: 1) i'm using somemodule!offset (i mean no func names or smth) 2) it would be very uncomfortable to get rid of them;