title: debug stack overflow in windows?
body: <p>So I'm trying to debug this strange problem where a process ends without calling some destructors...</p>
  
  <p>In the VS (2005) debugger, I hit 'Break all' and look around in the call stacks of the threads of the misteriously disappearing process, when I see this:</p>
  
  <p><a href="http://img6.imageshack.us/img6/7628/95434880.jpg" rel="nofollow noreferrer">smells like SO http://img6.imageshack.us/img6/7628/95434880.jpg</a></p>
  
  <p>This definitely looks like a SO in the making, which would explain why the process runs to its happy place without packing its suitcase first.</p>
  
  <p>The problem is, the VS debugger's call stack only shows what you can see in the image.</p>
  
  <p>So my question is: how can I find where the infinite recursion call starts?</p>
  
  <p>I read <a href="https://stackoverflow.com/questions/81202/segfault-on-stack-overflow" title="somewhere">somewhere</a> that in Linux you can attach a callback to the SIGSEGV handler and get more info on what's going on.</p>
  
  <p>Is there anything similar on Windows?</p>