[INFO] Syslog::PrintErr

[fvrmatteo]

Hi,

I wanted to let you know that while testing reFlutter (with @alximw) on Android 9/10 on an x86/x64 emulator, we realised that the call to Syslog::PrintErr was leading to a crash. The reason for the crash has been detailed here and a fix has already been released by the Dart maintainers. Sadly their policy is to update only the latest branch. An idea to avoid the bug in new and old releases would be to rely on OS::PrintErr instead.

[Impact-I]

Hi @fvrmatteo ,
Thank you for informing!

Yes, there is currently no x64 support due to an unknown glitch on the AVD. Looks like Syslog::PrintErr was the cause of the failure. I had to use it because OS::PrintErr is not available everywhere. I will try not to use Syslog::PrintErr in future releases.

As for the output to LogCat, it is unreliable. LogCat has an output limit - that's the only thing preventing me from making a new release with entry_point_offset output. It might be worth outputting information to a file, but Android's permission restrictions can get in the way of the user.

[fvrmatteo]

Hi!

Thanks for the feedback, glad this issue was indeed the one causing troubles for x86/x64. I think applying the fix just to Syslog::PrintErr in the same way other pieces of code are patched may solve the issue after all, without the need to use other functions.