C + + crash stack Information acquisition

Recently, when doing program exception stack information get related work, the previous article successfully wrote the dump file when the program Creash, and some cases write dump file is

No, for example, in the JNI development, C + + only do the underlying processing, and the entire project is the Android project, this time the dump file has no advantage, then only in the program

Creash when the memory information is printed out, get output to the file.
Here are some of the lessons I get when I do stack information acquisition:

Article 1: How to get the current call stack information in a program under Windows
Article 2: Let the program crash when a decent exit dump file
Article 3: Getting the program to collapse gracefully when exiting the callstack

As can be seen from the name, article 2 is generated dump file, my previous article can also generate dump file, but see the author of this article, it is absolutely

This article is also very detailed written, so special paste this connection, for everyone to learn.

Article 1 and article 3 I have successfully shown the stack information, but the situation is not quite the same, below I say a different place:
My environment: Win7 +vs2013 qt multithreaded Windows program

The article 1:main the active output stack information in the function, the result is successful, the information output at Creash is useless
Useful stack information can be output when the article 3:creash

Although they are all others ' documents, I can achieve some goals through what I describe.

C + + crash stack Information acquisition