summaryrefslogtreecommitdiff
path: root/Documentation/building/debugging-instructions.md
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/building/debugging-instructions.md')
-rw-r--r--Documentation/building/debugging-instructions.md8
1 files changed, 7 insertions, 1 deletions
diff --git a/Documentation/building/debugging-instructions.md b/Documentation/building/debugging-instructions.md
index 1a3b0234c9..9b3c2723d5 100644
--- a/Documentation/building/debugging-instructions.md
+++ b/Documentation/building/debugging-instructions.md
@@ -22,6 +22,12 @@ Debugging CoreCLR on Windows
Steps 1-8 only need to be done once, and then (9) can be repeated whenever you want to start debugging. The above can be done with Visual Studio 2013.
+### Using SOS with windbg or cdb on Windows ###
+
+If you know the path of the `sos.dll` for the version of your runtime, load it like `.load c:\path\to\sos\sos.dll`. Use can use the `lm` command to find the path of the "coreclr.dll" module. `.loadby sos coreclr` should also work.
+
+For more information on SOS commands click [here](https://msdn.microsoft.com/en-us/library/bb190764(v=vs.110).aspx).
+
Debugging CoreCLR on OS X
==========================
@@ -135,4 +141,4 @@ The "gcroot" command either crashes lldb 3.6 or returns invalid results. Works f
Loading Linux core dumps with lldb 3.7 doesn't work. lldb 3.7 loads OS X and FreeBSD core dumps
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
+For more information on SOS commands click [here](https://msdn.microsoft.com/en-us/library/bb190764(v=vs.110).aspx).