DllNotFoundException error message doesn't account for musl libc

[bording]

Currently, when there is a problem loading a library on linux, you get a System.DllNotFoundException with the following text:

IDS_EE_NDIRECT_LOADLIB_LINUX            "Unable to load shared library '%1' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: %2"

LD_DEBUG is something implemented in the glibc dynamic loader. If you're on a distro like Alpine, then you're using the musl libc dynamic loader, and it doesn't implement support for LD_DEBUG.

The error message is misleading in that case because setting LD_DEBUG doesn't do anything.

[danmoseley]

Apparently so https://www.musl-libc.org/doc/1.0.0/manual.html

Please do'nt remove the mention of LD_DEBUG though: it was added intentionally because users were commonly hitting some load error or another often in some library their own app pinvoked into, and did not know how to proceed without posting an issue here. Perhaps it can say "if you're using glibc" and possibly even suggest other means (strace?)