Emit an error message if the runtime fails to initialize, instead of just silently aborting

[JinShil]

See #95257 and #7740 and the various issue reports related to them.

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

[MichalStrehovsky]

Is there an example of a standard library (glibc, Rust stdlib, etc.) that prints to stderr if it fails to initialize? Trying to figure out if this is standard practice. Both good and bad things can happen from this.

[JinShil]

I think libc calls terminate, and users add a termination handler, but it's been a decade or two since I looked at the C runtime code. Is ASSERT_MSG or ASSERT preferred?

[JinShil]

Is ASSERT_MSG or ASSERT preferred?

It appears that would be pointless for release builds.

[JinShil]

This is the best I could think of to mimic a runtime initialization failure in C++:

#include <stdexcept>

struct Global 
{
    Global() 
    { 
        throw std::runtime_error("Init failure"); 
    }
};

Global g;

int main() 
{ 
    return 0;
}

That results in the following printed to stderr:

terminate called after throwing an instance of 'std::runtime_error'
  what():  Init failure
Aborted

Default Termination Handler:
https://github.com/gcc-mirror/gcc/blob/f7df645956459c559f254d622090d4dd09159890/libstdc%2B%2B-v3/libsupc%2B%2B/eh_term_handler.h#L35
https://github.com/gcc-mirror/gcc/blob/f7df645956459c559f254d622090d4dd09159890/libstdc%2B%2B-v3/libsupc%2B%2B/vterminate.cc#L44

[jkotas]

We do the same in front of other PalPrintFatalError, so this change is just going with the flow.

If we wanted to do something else, we should revisit all PalPrintFatalError+RhFailFast calls.