|
feline
Moderator
United Kingdom
12804 Posts |
 Posted - May 05 2009 : 4:27:45 PM
|
You can save out a mini dump file of a crashed / hung IDE or a running IDE process if Visual Assist X is somehow broken to help us debug the problem.
Using ProcDump
ProcDump from SysInternals is a small command line utility that can save out a mini dump from a running IDE, without needing to be installed first. It can be download from:
http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
To grab a dump of the current state of Visual Studio 2010 and save out the dump file called "vs2010_error_message.dmp" in the current directory:
procdump.exe devenv.exe vs2010_error_message.dmp
To grab a dump of Visual Studio 2008 when the process CPU usage hits 50% relative to a single core for 2 seconds, and save out the dump file called "vs2008_load_sol.dmp*" in the current directory:
procdump.exe -c 50 -u -s 2 devenv.exe vs2008_load_sol.dmp
To grab a dump of Visual C++ 6 when the IDE hangs (does not respond to window messages for at least 5 seconds), and save out the dump file called "c:\vc6_hang.dmp*" in the root of C drive:
procdump.exe -h msdev.exe vc6_hang.dmp
To grab a dump of Visual Studio 2003 when the IDE terminates, and save out the dump file called "vs2003_exit.dmp*" in the current directory:
procdump.exe -t devenv.exe vs2003_exit.dmp
Note ProcDump can be used with all versions of the IDE.
Setting Windows to save crash dumps
Windows Vista SP1 and Windows 7 can be configured so that Windows Error Reporting (WER) will save out a dump file when it detects an application crash. This is detailed here:
http://msdn.microsoft.com/en-us/library/bb787181%28VS.85%29.aspx
If you are using VS2005 or higher:
Launch a second instance of the IDE, but do not load any solution in this second instance.
Open the Tools menu (VS2005) or the Debug menu (VS2008 and higher) to select "Attach to Process..." (or just press Ctrl+Alt+P).
In the dialog that appears, select "devenv.exe" in the "Available Processes" list and press the "Attach" button.
If you are asked which program types you want to debug make sure "Native" is checked:
For VS2012 make sure that "Managed (v4.5, 4.0)" is also checked:
If the target process is not already hung or crashed, reproduce the problem at this point. If the problem is a hang, switch back to the debugger instance and break into the process using the "Break All" command from the Debug menu. If the problem is a crash, the debugger instance should automatically break in.
Now, create a dump file using the "Save Dump As..." item in the Debug menu and note where you save the DMP file. If you are given the option, select "no heap" when saving.
If the command is not available then you will need to use WinDbg to save out the mini dump file.
Using WinDbg - useful for VC6 or VS2003:
Unless this is already installed you will need to download and install the Microsoft Debugging Tools for Windows. The 32bit version is here:
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
and the 64bit version is here:
http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx
Run WinDbg via the Start menu:
Start -> All Programs -> Debugging Tools for Windows (x86) -> WinDbg
or directly run the program:
C:\Program Files\Debugging Tools for Windows (x86)\windbg.exe
Attach to the IDE process using the "Attach to a Process..." command from the File menu (alternatively, press F6). Select "msdev.exe" (VC6) or "devenv.exe" (VS2002 and above) from the list. It helps to have closed any extra instances of the IDE, so only the hung / problem IDE is in the list and you know you are selecting the correct process. Sorting the process list "By Executable" also helps.
If the target process is not already hung or crashed, reproduce the problem at this point. If the problem is a hang, switch back to WinDbg and break into the process. If the problem is a crash, WinDbg should become active.
In the WinDbg command prompt, type the command:
.dump /mdhiptu c:\va_problem.dmp
and then press Enter.
To close the IDE, select the "Stop Debugging" command from the Debug menu (or press Shift+F5).
To set the IDE running and detach the debugger, use the "Detach Debuggee" command from the Debug menu.
Sending us the resulting dump file
Then please zip up the mini dump file and attach it to a request for assistance (and if applicable include your support case number or the TOPIC_ID from the URL of your forum post in the subject):
http://www.wholetomato.com/support/contact.asp
|
Edited by - feline on Oct 15 2012 8:55:46 PM |
|
How do I save out a mini dump file?
Forum Locked
