Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>What CrashRpt does for emailing:</strong> </p> <p>The email system simply uses MAPI to send your email. Which would try to use your default mail client if you have one, and if it supports MAPI. Take a look at MailMsg.cpp for details. </p> <p><strong>Personal experience:</strong></p> <p>In my company's usage of CrashRpt, we modified it a bit though to call a web service that we created which submits the crash report. So we gutted the emailing code completely from CrashRpt. And instead we have in our bug tracking system a section for crashes that were auto submitted when crashes happen. </p> <p><strong>To find your problem:</strong></p> <p>I would maybe try to debug the CrashRpt code to see why it's giving you a save dialog. It should instead just open your default mail client. Maybe you have an older version of the library, or maybe the dialog resources are a little messed. Debugging the code will tell you this though. </p> <p>Most likely MailReport is being called but is failing. </p> <p>Set a breakpoint in the original <a href="http://code.google.com/p/crashrpt/" rel="nofollow noreferrer">CrashRpt code</a>'s CrashHandler.cpp at just after the DoModal:</p> <pre><code> mainDlg.m_pUDFiles = &amp;m_files; if (IDOK == mainDlg.DoModal()) { //Put breakpoint here &lt;--------- if (m_sTo.IsEmpty() || !MailReport(rpt, sTempFileName, mainDlg.m_sEmail, mainDlg.m_sDescription)) { SaveReport(rpt, sTempFileName); } } </code></pre> <p>Check to see why MailReport is not getting called. It's either the dialog resource, or your m_sTo is not filled or you can step through MailMsg.cpp and see where MAPI is failing. </p> <p><strong>Alternate solution:</strong></p> <p>An easy fix, if you find above that MailReport is being called, but not succeeding, is to instead just do a ShellExecute and specify a mailto:</p> <p>You could even try to use the MAPI method, but if that fails to do a mailto:</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload