Partager via

POP QUIZ: Why would you get this error from Windbg?

  • Article

Problem 1

So here is the scenario.  You open a dump from when you were experiencing a problem and try to run an SOS command and you see:

 0:024> !dumpheap -stat
Cannot get the ThreadStore, do you have symbols 
for the mscorwks/mscorsvr files?

What could be going on here?  Any suggestions on how to fix this?

Problem 2

Also, since we are talking about this, what about this error:

 0:024> !dumpheap -stat
Failed to find runtime DLL (mscorwks.dll), 0x80004005
Extension commands need mscorwks.dll in order 
to have something to do.

As always, post your thoughts in comments and I’ll turn them on and post the solution tomorrow.

kick it on DotNetKicks.com

Comments

  • Anonymous
    April 21, 2008
    You've been kicked (a good thing) - Trackback from DotNetKicks.com

  • Anonymous
    April 21, 2008
    The comment has been removed

  • Anonymous
    April 21, 2008
    The second error will occur if the dumheap command has been run too early before the .NET runtime DLL's have been loaded or if the dumpheap command is being run on a unmanaged process. The same issue might apply to Scenario #1 but I am not sure.. since never seen that message before

  • Anonymous
    May 04, 2010
    You would also get the second error if no managed code exists in the dump taken.  For example, taking a dump of a process that runs only native...