From f0183eb9020ae15c3ffcc91d2af844127216e3e3 Mon Sep 17 00:00:00 2001 From: Mike McLaughlin Date: Thu, 4 May 2017 10:58:58 -0700 Subject: [PATCH] Remove stale section on managed debugging. (dotnet/coreclr#11392) Commit migrated from https://github.com/dotnet/coreclr/commit/1ff9062d235630a3a47bffa6459549c669432c4a --- docs/coreclr/building/debugging-instructions.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/docs/coreclr/building/debugging-instructions.md b/docs/coreclr/building/debugging-instructions.md index 72f198b..1a3b023 100644 --- a/docs/coreclr/building/debugging-instructions.md +++ b/docs/coreclr/building/debugging-instructions.md @@ -136,10 +136,3 @@ Loading Linux core dumps with lldb 3.7 doesn't work. lldb 3.7 loads OS X and Fre just fine. lldb 3.8 loads all the platform's core dumps without problem. For more information on SOS commands see: https://msdn.microsoft.com/en-us/library/bb190764(v=vs.110).aspx - -Debugging Mscorlib and/or managed application -============================================= - -To step into and debug managed code of Mscorlib.dll (or the managed application being executed by the runtime you built), using Visual Studio, is something that will be supported with Visual Studio 2015. We are actively working to enable this support. - -Until then, you can use [WinDbg](https://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx) and [SOS](https://msdn.microsoft.com/en-us/library/bb190764(v=vs.110).aspx) (an extension to WinDbg to support managed debugging) to step in and debug the generated managed code. This is what we do on the .NET Runtime team as well :) -- 2.7.4