Typically libgcc_so.so is loaded by the linker, which uses an mmap call to map the binary into the address space. > The kernel keeps track of which file is map

Typically libgcc_so.so is loaded by the linker, which uses an mmap call to map the binary into the address space. > The kernel keeps track of which file is mapped where, and can detect when a request is made to map an already mapped file again, avoiding physical memory allocation if possible. Relevant stack overflow answer: https://stackoverflow.com/questions/61950951/linux-shared-library-loading-and-sharing-the-code-with-other-process#61956768 https://stackoverflow.com/questions/61950951/linux-shared-li...