-
-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firebird 5 crash on Android API level 34 #8110
Comments
Could you try to build with change |
I've never compiled Firebird, so if you can point me in the right direction for Android, I'd like to give it a try. |
Sorry, I was under impression that you build FB yourself. |
that would be perfect, I have a concurrent access test to the client library, that should allow me to validate this modification. |
On 5/14/24 17:45, Vlad Khorsun wrote:
Could you try to build with change |O_CLOEXEC| by |FD_CLOEXEC| ?
Strong feeling that FD_CLOEXEC should be used in this place.
Historically FD_CLOEXEC was fr a long time used only for 0 / not 0
check. Therefore no matter that FD_CLOEXEC has another value than
O_CLOEXEC that worked - but certainly FD_CLOEXEC is correct here.
I suppose we may simply replace it in the master branch.
|
Already pushed the branch with it :) |
On 5/14/24 18:12, Vlad Khorsun wrote:
Already pushed the branch with it :)
OK - extra check is always good thing ;)
|
Android builds are ready. |
Thank you very much, I'll test this on as many architectures as possible and report back. |
As far as I can tell, it works on Linux (x86_64), Mac Os (x86_64, aarch64), Android (armv7, armv8, x86_64). |
Thank you for investigating the problem and testing the fix |
We have reproduced the issue in the release version of Firebird 4. We couldn't find a download link for Firebird snapshots for Android. If you can send us a download link when you fix the issue for Firebird 4 - we'll test it. |
We faced the same problem with FireBird client 3.0.11 for Android - will the fix be backported to FB 3 ? |
Backported into 3.0.12 and 4.0.5 |
Steps to reproduce.
The problem also occurs on a physical device. I have not been able to reproduce the problem on versions below 34.
Logcat
The text was updated successfully, but these errors were encountered: