[android] Add runtime logging support for CoreCLR on Android

[ivanpovazan]

Description

This issue is made for tracking necessary work for enabling runtime logging for CoreCLR on Android.

Logging

Currently, most of the messages logged by the runtime end up in /dev/null (either because they
are disabled in release build or because they log to stdio which doesn't work on Android).

Logcat is the only way to get information from remote devices, especially via Google Play Console.

We should log to logcat:

• C++ exception messages
• abort() messages / fatal errors
• warnings
• errors

A subsystem should be added which will provide a single function that will do actual output, implementation of which
will be specific to the platform. API should allow specification of severity, the actual message, and possibly a flag
to indicate whether the process should be aborted (the decision might also be based on the severity). Severity should
be shared between all targets, which then can (if needed) translate it to the target platform's value(s), if any.

Tasks

• Enable JIT logging: [android][coreclr] Make coreclr build specify HOST_ANDROID and include Android logging APIs #112677
• Fatal error logging: [Android] Add callback to host-runtime contract for getting assembly data #112705
• Enable runtime logging
  • Necessary bits already addressed in: [Android] Add callback to host-runtime contract for getting assembly data #112705, pulled out in cf2aae6
• TBD

References on runtime logging

https://github.com/dotnet/runtime/blob/9ff850ea5d29f487961d1c773bd495630aa8d2ea/docs/design/coreclr/botr/logging.md

[ivanpovazan]

/cc: @janvorli @elinor-fung @grendello @lateralusX

Please fill in the description as you see fit

[am11]

I think it would be nice to consolidate all logging implementation in src/native/minipal, where we have various similar shared components.

log/assert like native code in the repo, which are overlapping:

runtime/src/mono/mono/utils/mono-log-android.c

Line 39 in 0b80e90

mono_log_write_logcat (const char *log_domain, GLogLevelFlags level, mono_bool hdr, const char *message)

runtime/src/mono/mono/utils/mono-logger-internals.h

Line 154 in 0b80e90

void mono_log_open_logcat (const char *path, void *userData);

runtime/src/native/libs/System.Security.Cryptography.Native.Android/pal_err.c

Line 31 in 0b80e90

#define SEE_LOGCAT_MESSAGE_LEN (int32_t)(sizeof(see_logcat_message))

runtime/src/mono/mono/utils/mono-logger.c

Line 136 in 0b80e90

logger.opener = mono_log_open_logcat;

runtime/src/coreclr/inc/debugmacros.h

Line 37 in 0b80e90

#define _ASSERTE_MSG(expr, msg) \

runtime/src/native/libs/Common/pal_utilities.h

Line 31 in 0b80e90

#define assert_msg(cond, msg, val) do \

[jkotas]

Enable runtime logging

The most valuable form of runtime logging is stresslog. Stresslog is high-performance logging that is not printed to console. Instead, it is recorded in a circular buffer that can be extracted from a crash dump via SOS DumpLog command. Stresslog is compiled into release builds and we depend on it to diagnose toughest bugs like intermittent crashes.

It would be great if we can create a documented workflow for how to use stresslog on Android.