How can I test Windows Error Reporting? -


My company is connected through Windows Error Reporting We add some extra data to our crash reports using WERRegisterMemoryBlock Obviously we want to make sure that it is working before sending our next version. How can we test it?

Is there a way to properly preview it that is being sent? Does it really reproduce that we're going to be able to get from Winqual?

Alternatively, can we generate a real report from the developer machine, can get the report again from Winqual? How do we differentiate this test case from all our vinkal data?

[...] Can we generate a real report from the developer machine, Can you get reports again? Winqual?

  • Prepare a special trial version of your application
  • Upload WER for this trial version
  • with error reporting Crash test version on the machine
  • Check Winqual, should display a report after a few days
  • If the report does not already come with CAB data, additional data Enable the request (in the queue)
  • Error reporting enabled
  • Check Winqual, after a few days, a report with cab data should wait for you
  • Download the cab data and check that What / what you need in it (you will need to use WinDbg to get the full picture, not as complete with the MiniDump as VS as WinDbg)

We will investigate this case How will programmed differently from all visual data?

  • The test version has a special name and version (EXE name and * .rc)
  • Just a different "product name" and "product version" ( = WER friendly name) is not enough to get an extra event ID / bucket, but
for an additional EXE name plus "mapping" "Product Name" for application mapping

Comments

Popular posts from this blog

windows - Heroku throws SQLITE3 Read only exception -

lex - Building a lexical Analyzer in Java -

python - rename keys in a dictionary -