Debug stack overflow on windows?

Question

So, I am trying to debug this strange problem when the process terminates without calling any destructors ...

In the VS (2005) debugger, I click "Break All" and look around at the call tables of the process flows with fading out when I see this:

it smells SO http://img6.imageshack.us/img6/7628/95434880.jpg

It definitely looks like SO in the making process, which explains why the process goes to its happy place without first packing its bag.

The problem is that the VS debugger call stack only shows what you see in the image.

So my question is: how can I find where the infinite recursion call begins?

I read somewhere that on Linux you can attach a callback to the SIGSEGV handler and get more information about what is going on.

Is there something similar on windows?

Answer 1

To control what Windows does in case of an access violation ( SIGSEGV-equivalent), call SetErrorMode(pass it a parameter of 0 to cause a pop-up window in case of errors, which allows you to connect it using a debugger.)

. , , VS. ( /F ), , , VS . std:: basic_filebuf < > :: flush() ( ).

Answer 2

, , , - , , , .

Windows - , VS (), , , ( , , - ).

Answer 3

, , , . ? , .

, . printf/OutputDebugString ( , ). - , , , , - , .

, , , - , , " ".

Answer 4

, Windows , .

, , , . , - , . , , , .

Sleep() , . , .

Answer 5

. . , . WER, . ?