Unable to read crash dump in windbg

Question

I have been getting a stackoverflow exception in my program which may be originating from a thirdparty libary, microsoft.sharepoint.client.runtime.dll.

Using adplu

Answer 1

This page provides lots of useful information and method to analyze the problem. http://www.dumpanalysis.org/blog/index.php/2007/09/11/crash-dump-analysis-patterns-part-26/

Answer 2

The problem you are facing is that the process is 32-bit, but you are running on 64-bit, therefore your dump is a 64-bit dump. To make use of the dump you have to run the following commands:

.load wow64exts
.effmach x86
!analyze -v

The last command should give you a meaningful stack trace.

Answer 3

You didn't mention if your code is managed or unmanaged. Assuming it is unmanaged. In debugger:

.symfix
.reload
~*kb

Look through the call stack for all threads and identify thread that caused SO. It is easy to identify the thread with SO, because the call stack will be extra long. Switch to that thread using command ~<N>s, where is thread number, dump more of the call stack using command k 200 to dump up to 200 lines of call stack. At the very bottom of the call stack you should be able to see the code that originated the nested loop.

If your code is managed, use SOS extension to dump call stacks.