Documentation too shallow to replicate for how-to LLDB dotnet process memleaks

I wasn't able to use LLDB to debug dotnet application for unloadability memory leak. Documentation at first is unclear what LLDB is in the first place and how it works, secondly after `dotnet-sos install`, I tried to use LLDB SOS tools and getting
"Failed to find runtime module (libcoreclr.so), 0x80004005" all the time.

Dotnet SDK is installed and PATH recognizable. Really unsure if LLDB is able to attach to existing processes, or does LLDB starts application as child process.

Clear unloadability code examples are great, but if you read article from top to bottom, it is really hard to replicate the experiment while trying to use LLDB, the first time ever seen tool.

Thanks for making dotnet assemblies unloadable.

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: f3283764-f15a-fa5f-5106-6f294c780f7b
* Version Independent ID: b03cedce-9074-9686-0b31-045b2b4c862d
* Content: [How to use and debug assembly unloadability in .NET Core](https://docs.microsoft.com/en-us/dotnet/standard/assembly/unloadability)
* Content Source: [docs/standard/assembly/unloadability.md](https://github.com/dotnet/docs/blob/main/docs/standard/assembly/unloadability.md)
* Product: **dotnet-fundamentals**
* GitHub Login: @janvorli
* Microsoft Alias: **janvorli**