docs: Update README and compilation documentation

Author: guyush1

README.md

@@ -44,6 +44,7 @@ This is where `gdb-static` comes in! We provide static builds of `gdb` (and `gdb
 </summary> <br />
 
 - **Static Builds**: No dependencies, no installation, just download and run!
+- **Musl Based**: We use Musl in order to create distribution-independant binaries that can work anywhere.
 - **Latest Versions**: We keep our builds up-to-date with the latest versions of GDB.
 - **Builtin Python (Optional)**: We provide builds with Python support built-in.
 - **XML Support**: Our builds come with XML support built-in, which is useful for some GDB commands.

compilation.md

@@ -14,13 +14,15 @@ Please note that when specifying a compilation dir throughout the compilation pr
 Instead, always use absolute paths.
 
 Examples to the <VARIABLES> throughout the script:
-- <CROSS_COMPILER_C> - arm-linux-gnueabi-gcc
-- <CROSS_COMPILER_CPP> - arm-linux-gnueabi-g++
-- <HOST_NAME> - arm-linux-gnueabi
+- <CROSS_COMPILER_C> - arm-linux-musleabi-gcc
+- <CROSS_COMPILER_CPP> - arm-linux-musleabi-g++
+- <HOST_NAME> - arm-linux-musleabi
 - <COMPILATION_DIR_PATH> - /home/username/projects/libgmp-x.y.z/build-arm/
 
-Environment info:
-- glibc version: 2.39-0ubuntu8.3 (NOTE: When i compiled gdb using an older glibc, such as the one i had in my ubuntu-20.04 machine, i received a segfault in gdb, so the libc version is important!).
+## Choosing the right compiler
+
+It is recommended to use a musl-based compiler. Unlike glibc, musl is not dependant on your distribution.
+Using regular gcc that is glibc based should work most of the time, but we had some people reporting crashes mainly in gdbserver, so we switched to musl-based toolchains.
 
 # Compiling gdb statically to the host platform