Alexis Christoforides

The stack trace seems wrong: From the text on stdout, we can see that mono_handle_native_crash progressed past the call to `mono_dump_native_crash_info`, and must have hung on `mono_post_native_crash_handler`

@rolfbjarne I could reproduce this in an equivalent Xamarin.Mac app too, since [this commit](https://github.com/xamarin/xamarin-macios/commit/4be1cd723b3273b9c2f1b80f78d67e1eb641e618) has enabled crash chaining there too. Signal chaining is not involved, so removing this call should...

From the function's comment, it `If crash chaining is enabled, it will first print its crash information and then try to chain with the native handler.` Practically, this just decides...

https://github.com/mono/mono/pull/19891 is related as a case where `mono_chain_signal` wasn't being called after some SIGSEGV crashes. Not sure yet if this would also fix the issue, will test presently. Also, I...

Could we surface this as opt-in XM/XI API so only the users who need it turn it on?