问题描述
什么情况是我们有一个联系人同步的应用程序。不久之后pressing启动了同步的主要逻辑应用程序中的按钮，该应用程序停止运行，且Windows（7在这种情况下）说，我们的应用程序已停止工作之后，唯一的可能就是关闭应用程序通过了题为按钮关闭程序。
What happens is we have a contact sync application. Soon after pressing a button that starts the main logic of the syncing in the application, the application stops working and Windows (7 in this case) says our application "has stopped working" after which the only possibility is to close the application via a button entitled "Close the application".
一个奇怪的是，在我的开发机，应用程序工作正常。它不会崩溃，没有任何抛出任何错误。但是，当打包为一个安装，并安装在其他计算机上。它只停止工作，如上所述。
One weird thing is that, on my development machine, the application works fine. It does not crash, does not throw any errors whatsoever. But, when packaged as an installer and installed on other machines it does stop working as described above.
请让我知道哪些应用程序，我可以使用调试这更好的，如何找到更多关于这个错误，是什么触发它，它如何能得到解决等。
Please let me know what apps I can use for debugging this better, how to find out more about this error, what is triggering it, how it can be solved etc.
在此先感谢。
后修改的
这是什么打印在事件查看器日志：
This is what is printed out in the event viewer log:
Faulting application name: ourappname.exe, version: 1.2.9.0, time stamp: 0x4f3926c8
Faulting module name: ntdll.dll, version: 6.1.7600.16915, time stamp: 0x4ec49caf
Exception code: 0xc0000374
Fault offset: 0x000c33bb
Faulting process id: 0xecc
Faulting application start time: 0x01ccea61773d12e0
Faulting application path: C:\Program Files\path\to\ourappname.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: bb3977f0-5654-11e1-9a84-0800275ba797
帮助吗？
推荐答案
设置一个全球未捕获的异常处理程序并记录错误。良好的措施，您可以编写应用程序和使用的内存转储的WinDbg 一起的得到相当precise看看发生了什么事情在你的应用程序（dbghelp.dll船旁边的WinDbg中Windows调试工具）。
Set up a global uncaught exception handler and log the error. For good measure, you can write a memory dump of your application and use WinDbg along with SOS.dll to get a rather precise look at what's going on in your app (dbghelp.dll ships alongside WinDbg in Debugging Tools for Windows).
这篇关于我们的应用程序崩溃 - 如何找到失事的原因是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！