Closed mnyoshie closed 7 months ago
Maybe this has something to do:
Edit: Hmm but the build.sh don't include those. https://github.com/termux/termux-packages/blob/master/packages/mono/build.sh
Maybe a problem in the upstream?
It sends such information to Android log. Use logcat
to see your exception. (marking as not a bug)
Meanwhile I tried to replace http://blahblah.xxxx
with http://termux.dev
and got an exception that TLS support is not available. So the networking support can be considered as broken or incomplete, but I think this is for another ticket.
I think default to logcat
is specific to Android OS target. This can be changed by patching sources.
Oh I see... Seems like logging with https://github.com/mono/mono/blob/main/mono/utils/mono-log-common.c instead of https://github.com/mono/mono/blob/main/mono/utils/mono-log-android.c should do the trick I believe.
The common logging functions are set in last https://github.com/mono/mono/blob/0cb9dac52f9a3280fe167e3aefd194b1e4dd26c3/mono/utils/mono-logger.c#L181-L184
Problem description
mono
does not output an error on stderr when it receives an "Unhandled Exception". (mono$?
returns 1). But those "Unhandled Exception" message can be seen on strace.What steps will reproduce the bug?
What is the expected behavior?
mono
must explicitly output what got wrong.System information
termux-info: