Advertisement

04.03.2008 at 01:25AM PDT, ID: 23292011
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.9

How to get minidump programmatically on demand?

Asked by pepr in Windows Programming, Miscellaneous Programming, C++ Programming Language

Tags: , ,

Hi experts,

I want to enhance the capability of our application to report the problem when something wrong happen. So far, we use exceptions, capture them as soon as possible (but not sooner than necessary) and write the related info into a proprietary log file. It works fine and saved a lot of problems for us. However, when something happens in the very frequently used part of the application, we feel we need more information from where the code was called, etc.

Digging around, I have found the notion of minidump (the Microsoft implementation; I am very new to it). To understand it better, I was searching for some bare-bone example that shows the use. So far I have found the following tiny example
http://www.clausbrod.de/cgi-bin/view.pl/Blog/DefinePrivatePublic200706#DefinePrivatePublic20070627_Thin
and some not so brief examples. (I did not try all the related things like building the applications with full .pdb file and off-line (post mortem) debugging -- just have some basic understanding.)

However, the examples show how to solve the situation when the exceptions are not captured at all -- based on usage of the
    SetUnhandledExceptionFilter(myFilterFunction);
that gets _EXCEPTION_POINTERS *exc_ptr from the kernel (or whatever) and this is passed to the MiniDumpWriteDump() function.

I would like to do the same when I catch a standard C++ exception. How to get the _EXCEPTION_POINTERS for the standard exception? Am I walking the correct path to the solution? Is it possible to use such minidump (with the .pdb file) for discovering where the problem happened (like the call stack, etc.)? Some working examples, tutorials?

Thanks for any info,
   PetrStart Free Trial
[+][-]04.03.2008 at 09:18AM PDT, ID: 21274160

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Windows Programming, Miscellaneous Programming, C++ Programming Language
Tags: minidump, post-mortem debug, call stack
Sign Up Now!
Solution Provided By: jkr
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_EXPERT_20070906