Export/import stack trace in VS2010 - visual-studio-2010

In Visual Studio 2010, is it possible to export and import a stack trace as a file, for debugging purposes?
Currently, we inlcude the stack trace in an email, but it would be easier on the eyes and mind if we were able somehow pull it in to visual studio and interact with it like normal!

ReSharper has an option to Open a Stack Trace in Visual Studio

Related

How to show Call Stack windows in Visual Studio 2017

I expected to find them under the Debug menu, then Windows but the call stack isn't there in visual studio 2017
It's under Debug > Windows, but you only see it when your application is running:
When your application isn't running, the menu is quite short:

Logging the flow of control in Microsoft Visual Studio Ultimate 2013

I am working with Microsoft Visual Studio Ultimate 2013, on an extremely large code base.
I am currently trying to debug an issue, but i am unable to place breakpoints correctly, and relying on pure guesswork and hit-n-trial.
Is there any way by which we can list the entire trace of flow of control in VS 2013?
(The entry and exit of the functions which are called)
(PS: There are no explicit logging statements written in the code).

sos.dll usage in visual studio 2013

When I am reading docs about sos.dll #MSDN, encounter a note says
If you are using Visual Studio 2013, SOS.dll is supported in the Windows Debugger within Visual Studio
I know how to use sos.dll in the immediate window in Visual Studio 2012. But how to use sos.dll with visual studio 2013 debugger?
From MSDN documentation of What’s New for the Debugger in Visual Studio 2013 (Excerpt from the part Debug With Debugging Tools for Windows)
The SOS.dll (SOS Debugging Extension) that helps you debug managed
programs in WinDbg, is not available from the Visual Studio IDE. See
Debugging Managed Code Using the Windows Debugger
Looks like you may need to load them separately as being said Here
I couldn't get sos.dll to load in Visual Studio 2013 no matter what I tried.
I've resorted to good old WinDbg instead. I know it's not an ideal answer, but it appears to be the only possible solution to debugging with sos.dll. I'd really like to use sos.dll in Visual Studio 2013, but WinDbg isn't so bad once you learn its basics. It's actually very powerful, even if you know very little about the unmanaged world (like me).
How to load SOS in WinDbg
Yes you can use SOS from VS 2017. But you will need to install windows driver kit (WDK). Here is a screenshot of me debugging a process with command line debugger within VS 2017.
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/setting-up-user-mode-debugging-in-visual-studio

Visual Studio 2013 Update 1 Debugger Crashing

I recently installed Update 1 for Visual Studio 2013. Every time my program throws an exception, the Visual Studio debugger crashes - whether or not the exception is handled.
Visual Studio also crashes whenever it hits a breakpoint.
The Windows Error Reporting dialog pops up and gives the options to debug or restart Visual Studio. If I click debug and and open with VS, it also crashes - debugging itself! This is leading me to believe that there is not a problem with my app, but rather with Visual Studio.
Visual Studio Professional 2013 (12.0.30110.00 Update 1)
Windows Server 2012 R2 x64
Any ideas?
The problem, it turns out, was that I had installed a trial version of Redgate Tools' .NET Reflector. The trial's expiration had coincided with my installation of Update 1. .NET Reflector was throwing a NullReferenceException and hence crashing Visual Studio.
The solution was simple: disable or uninstall the .NET Reflector extension.
My proposal is: get more data about the crash and see whether it's caused by Visual Studio itself or any plugins which might not be compatible any more.
Set up the registry for Windows Error Reporting to store local dump files, reproduce the crash and analyze the dump in WinDbg (because Visual Studio is not working well).
Some steps in WinDbg:
open crash dump
.symfix c:\mysymbols
.reload
.exr -1
.loadby sos clr (if it's a .NET exception)
!pe (if it's a .NET exception)
!clrstack (if it's a .NET exception)
I also get Problems with IDE crashing after installed "update 1". My Workaround: uninstall that update. It is really Buggy and NOT production ready. Maybe it is caused by a Extension, but I dont have time to debug Tools I have to use to get my work done, I Need working Tools.
I've been stuck in this problem for 3 days until I discovered that the problem was in try-catch blocks. Viewing this article: http://msdn.microsoft.com/en-us/library/vstudio/0yd65esw%28v=vs.110%29.aspx, I realized the importance of not leaving a "catch" empty.
Well, this problem happened to me while developing a simple sequential workflow SharePoint 2013 in Visual Studio 2013 in "OnTaskChanged" methods.
I hope the answer may help someone else.

vsjitdebugger alternative?

vsjitdebugger gets more annoying when i switched to windows 7. :(
i'm a commandline person (vim, msbuild and vsjitdebugger) when developing .NET. I'm looking for a better vsjitdebugger alternative that automatically attaches the application to visual studio (or any application that is less annoying than vsjitdebugger.)
TIA :)
From here
To begin Just-In-Time debugging when
an error occurs
In the Just-In-Time Debugging dialog
box, in the Possible Debuggers list,
click New instance of Visual Studio
2010 or click an instance of Visual
Studio 2010 that is already running.
To use Visual Studio automatically for
all future crashes, click Set the
currently selected debugger as the
default.
If you want to choose what types of
code you will be able to debug, click
Manually choose the debugging engines.
If you do not choose this option,
Visual Studio automatically selects
the appropriate debug engines for the
type of code in your program.
Click OK.

Resources