All geek questions in one place

Memory Dump Does Not Show Details for IIS Failure

I published a new version of my web application. Something in the new version caused IIS to crash, and I cannot determine which code is causing it.

Using the information here , I have enabled automatic crash dumps.

Then, after successfully creating the crash dump, I used the instructions of this question , using WinDbg, to try to determine what happened.

After I found the thread that crashed and ran pe (thread) on it, it shows that this is the result of StackOverflow. However, the details are not indicated:

0:064> !pe 00000001bfda01f0 Exception object: 00000001bfda01f0 Exception type: System.StackOverflowException Message: <none> InnerException: <none> StackTrace (generated): <none> StackTraceString: <none> HResult: 800703e9

As you can see, there is no exception or stacktrace information.

Is there any step that I'm missing to make sure this information either captures or appears in WinDbg?

+4
source share
1 answer

As I found a StackOverflow exception source in the past:

  • Open WinDbg and Open Crash Dump and find the dump file.
  • At the command prompt, enter .loadby sos clr
  • Now enter !CLRStack

Source: http://mikesmithdev.com/blog/debug-stack-overflow-exception/

+5
source

Source: https://habr.com/ru/post/1493510/

More articles:


All Articles