diff options
| author | Eric Mellino <erme@microsoft.com> | 2017-04-28 05:50:23 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-04-28 05:50:23 +0300 |
| commit | 70186262dcd2cea4944b5d5768d67d156bda61dc (patch) | |
| tree | d6765b2ccd62d2e0c8ed698acfdef181c021c98a /Documentation/debugging | |
| parent | c14185223acc62525b0af0887ebc4d3d4ecfeac7 (diff) | |
Add a missing word.
Diffstat (limited to 'Documentation/debugging')
| -rw-r--r-- | Documentation/debugging/unix-instructions.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/debugging/unix-instructions.md b/Documentation/debugging/unix-instructions.md index de8339ee82..62a942d3cd 100644 --- a/Documentation/debugging/unix-instructions.md +++ b/Documentation/debugging/unix-instructions.md @@ -26,7 +26,7 @@ It is also possible to debug .NET Core crash dumps using lldb and SOS. In order - Build coreclr at the matching commit. In order to determine which commit was used to build a version of libcoreclr.so, run the following command: `strings libcoreclr.so | grep "@(#)"` -Once you have everything listed above, you are ready to start debugging. You need to specify an extra to lldb in order for it to correctly resolve the symbols for libcoreclr.so. Use a command like this: +Once you have everything listed above, you are ready to start debugging. You need to specify an extra parameter to lldb in order for it to correctly resolve the symbols for libcoreclr.so. Use a command like this: ``` lldb -O "settings set target.exec-search-paths <runtime-path>" --core <core-file-path> <dotnet-path> |