获取在启动时崩溃的进程的转储 [英] Getting a dump of a process that crashes on startup

问题描述

在我无法访问的客户机器（WinXP SP2）上，我有一个Win32 EXE（非托管C ++），在启动时崩溃。我想解决这个问题的最好方法是获取一个（mini-）转储，并用windbg或类似的分析它。

现在，我通常会告诉客户安装Windows的调试工具并运行

  cscript adplus.vbs -crash 
  pre> 
 
 
但是，您似乎无法对启动时崩溃的应用使用adplus（ http://support.microsoft.com/kb/q286350/ 说在以下情况下不要使用ADPlus：如果您必须排除程序或进程的故障在启动期间意外退出）。同样的文章说使用用户模式过程转储，但我未能成功安装。
 
 
 
任何想法如何获得一个进程崩溃在Win32上？
解决方案
您可以安装 WinDBG ，然后使用图像文件执行选项，并在进程启动后将WinDBG设置为打开。然后运行崩溃进程，WinDBG会立即打开。按  g  （Go）并等待进程崩溃，然后键入 *。dump / mfh [dump file name] * 。现在你有转储文件，你可以调试。
 
On a customer machine (WinXP SP2) to which I have no access, I have a Win32 EXE (unmanaged C++) that crashes on startup. I guess the best way to troubleshoot this is to obtain a (mini-)dump and analyze it later with windbg or similar.

Now, I would normally tell the customer to install Debugging Tools for Windows and run
cscript adplus.vbs -crash
However, it appears that you can't use adplus for apps that crash on startup (http://support.microsoft.com/kb/q286350/ says that "Do not use ADPlus in the following situations: If you must troubleshoot a program or process that quits unexpectedly during startup"). The same article says "use User Mode Process Dump", but I failed to install it successfully.

Any idea of how to get a dump of a process that crashes on startup on Win32?
解决方案
You can install WinDBG on the client machine and then use "Image File Execution Options" and set WinDBG to open once that the process has started. Then run the crashing process and WinDBG will open up immediately. press g (Go) and wait for the process to crash then type *.dump /mfh [dump file name] *. Now you have dump file that you can debug.

                        
这篇关于获取在启动时崩溃的进程的转储的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！