Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

How to save Visual Studio debug session after bomb for later analysis?

Posted on 2011-09-30
3
280 Views
Last Modified: 2013-12-16
I'm test running a program in Visual Studio. I came across an unusual fatal exception. I would like to save everything so I can come back Monday and look at it.

Is there a way to save everything, the current state, all the threads, etc. so I can analyze it later?

Because I'm about to leave for the weekend.
0
Comment
Question by:deleyd
  • 2
3 Comments
 
LVL 40

Assisted Solution

by:Jacques Bourgeois (James Burger)
Jacques Bourgeois (James Burger) earned 333 total points
ID: 36895310
Put the computer in Sleep mode. You have that on the Logoff menu. It turns down everything, but leaves just enough current flowing to keep the microprocessor and memory alive. Moving the mouse or hitting the space bar a few times on Monday whould reawake the computer to the state it was on when you left it. I almost never ShutDown my computer, it always goes to sleep, and very rarely will it not awake in the state it was in.
0
 
LVL 5

Accepted Solution

by:
MikkelAStrojek earned 167 total points
ID: 36896170
Actually intellitrace available in vs2010 should be able to do just that, havn't tried it though
0
 
LVL 40

Assisted Solution

by:Jacques Bourgeois (James Burger)
Jacques Bourgeois (James Burger) earned 333 total points
ID: 36896904
IntelliTrace is a good tool, but you need the costly Ultimate edition to have it.

And I am not sure that it would answer the need. I think that he wanted to save the application in the state it was, in debugging mode. IntelliTrace just record what happens in a file. It is superb to review what happened before the application crashed, but does not give you the same tools as the debugger. For instance, to prevent it from gobbling up too much processor time or give you too much information, you must filter the type of information you want it to grab. Sometimes, you filter the reason for the problem. In the debugger, you have access to everything but the history.

In my opinion, these are 2 complementary tools.
0

Featured Post

Master Your Team's Linux and Cloud Stack!

The average business loses $13.5M per year to ineffective training (per 1,000 employees). Keep ahead of the competition and combine in-person quality with online cost and flexibility by training with Linux Academy.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This document covers how to connect to SQL Server and browse its contents.  It is meant for those new to Visual Studio and/or working with Microsoft SQL Server.  It is not a guide to building SQL Server database connections in your code.  This is mo…
Today I had a very interesting conundrum that had to get solved quickly. Needless to say, it wasn't resolved quickly because when we needed it we were very rushed, but as soon as the conference call was over and I took a step back I saw the correct …
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question