VSadov/Satori
1
0
Fork 0
mirror of https://github.com/VSadov/Satori.git synced 2025-06-12 10:40:30 +09:00
Code Activity

Repoint urls in docs (#73766)

Browse source
This commit is contained in:
N0D4N 2022-08-15 03:56:07 +03:00 • committed by GitHub
parent 069460c6ef
commit 126045ca05
Signed by: github
GPG key ID: 4AEE18F83AFDEB23
81 changed files with 175 additions and 175 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/workflow/debugging/coreclr/debugging.md
View file

@ -87,14 +87,14 @@ When there's source code change in coreclr, invoke the 'Install' command again t
### Using SOS with windbg or cdb on Windows ###
See the SOS installation instructions [here](https://github.com/dotnet/diagnostics/blob/master/documentation/installing-sos-windows-instructions.md).
See the SOS installation instructions [here](https://github.com/dotnet/diagnostics/blob/main/documentation/installing-sos-windows-instructions.md).
For more information on SOS commands click [here](https://github.com/dotnet/diagnostics/blob/master/documentation/sos-debugging-extension-windows.md).
For more information on SOS commands click [here](https://github.com/dotnet/diagnostics/blob/main/documentation/sos-debugging-extension-windows.md).
Debugging CoreCLR on Linux and macOS
====================================
See the SOS installation instructions [here](https://github.com/dotnet/diagnostics/blob/master/documentation/installing-sos-instructions.md). After SOS is installed, it will automatically be loaded by lldb.
See the SOS installation instructions [here](https://github.com/dotnet/diagnostics/blob/main/documentation/installing-sos-instructions.md). After SOS is installed, it will automatically be loaded by lldb.
Only lldb is supported by SOS. Gdb can be used to debug the coreclr code but with no SOS support.
@ -113,7 +113,7 @@ See https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-sos for info
### Debugging core dumps with lldb
See this [link](https://github.com/dotnet/diagnostics/blob/master/documentation/debugging-coredump.md) in the diagnostics repo.
See this [link](https://github.com/dotnet/diagnostics/blob/main/documentation/debugging-coredump.md) in the diagnostics repo.
Disabling Managed Attach/Debugging
==================================

4
docs/workflow/debugging/libraries/unix-instructions.md
View file

@ -15,7 +15,7 @@ It is also possible to debug .NET crash dumps using lldb and SOS. In order to do
- The crash dump file.
- On Linux, there is an utility called `createdump` (see [doc](../../../design/coreclr/botr/xplat-minidump-generation.md "doc")) that can be setup to generate core dumps when a managed app throws an unhandled exception or faults.'
There are instructions for installing lldb and SOS [here](https://github.com/dotnet/diagnostics/blob/master/documentation/sos.md).
There are instructions for installing lldb and SOS [here](https://github.com/dotnet/diagnostics/blob/main/documentation/sos.md).
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:
@ -29,7 +29,7 @@ lldb-3.9 -O "settings set target.exec-search-paths <runtime-path>" --core <core-
lldb should start debugging successfully at this point. You should see stacktraces with resolved symbols for libcoreclr.so. At this point you can begin using SOS commands provided you've set it up as described in the links.
Also see this [link](https://github.com/dotnet/diagnostics/blob/master/documentation/debugging-coredump.md) in the diagnostics repo.
Also see this [link](https://github.com/dotnet/diagnostics/blob/main/documentation/debugging-coredump.md) in the diagnostics repo.
##### Example