Is there a cap on the number of modules WinDbg can see?
Posted
by
Bethor
on Stack Overflow
See other posts from Stack Overflow
or by Bethor
Published on 2011-11-18T17:48:35Z
Indexed on
2011/11/18
17:51 UTC
Read the original article
Hit count: 230
Does anyone know if there is a cap on the number of DLLs WinDbg can see ? I believe Visual Studio was once capped at 500 but I can't find a source for this claim outside of some second hand accounts at work.
I'm trying to debug a hairy scenario and WinDbg's stack trace is incomplete. According to Process Explorer, the module I'm interested in is loaded but it doesn't show up in the output of 'lm' in WinDbg.
Suspiciously, said output is exactly 500 modules long, even though I know there are many more than that loaded, leading me to believe WinDbg isn't seeing DLLs beyond the first 500. Can anyone confirm ? Or suggest some other reason why a loaded module might not show up in 'lm' ?
© Stack Overflow or respective owner