-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fixed the native crash happening on Android. #116
Open
MohitMaliFtechiz
wants to merge
2
commits into
main
Choose a base branch
from
fix_native_crash_on_android
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't see how this could work in the pre-C++-14 language standard that I am more or less familiar with.
SAFE_THIS
has to be an expression but it doesn't seem to expand to code that can be considered an expression according to the language specification. I tried to quickly skim through https://en.cppreference.com/w/cpp/language/expressions but couldn't find anything that allows to consider this code valid in modern c++.In other words, I am puzzled how this code compiles (in the context of the change in
lib/src/main/cpp/libzim/archive.cpp
).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@veloman-yunkan This code is made by @mgautierfr, he can better explain this, and i am not very much familiar with C++.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that @veloman-yunkan understand how it works :)
#define FOO BAR
make every instance ofFOO
literally replaced byBAR
.So something like
THIS->getEntryByPath(...)
is replaced bygetPtr<NATIVE_TYPE>(env, thisObj)->getEntryByPath(...)
. And it compiles becausegetPtr
is a function returning a pointer.With your define of
SAFE_THIS
we haveSAFE_THIS->getEntryByPath(...)
replaced by:And, as @veloman-yunkan, I don't know how this code can be compiled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mgautierfr
SAFE_THIS
also uses thegetPtr<NATIVE_TYPE>(env, thisObj)
to get the pointer, and if this method returns thenullptr
it throws the error which will be caught in thearchive.cpp
.Also, in the archive.cpp
SAFE_THIS
returns the archive.I think that's why this code was compiled without any error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SAFE_THIS
is not a function. It is a macro (ie. textual replacement)It appears that we are facing a statement expression (https://stackoverflow.com/questions/8344101/what-is-it-called-when-a-block-returns-a-value) which is not a standard C++ code but a gcc extension.
This explain why it works. However, I not really confident to use a non standard c++ here, especially as we have a better alternative.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ohh okay got it. @mgautierfr So we can remove this
SAFE_THIS
as it is non-standard. In this PR I have updated thegetPtr
method if that is null it returns thenullptr
which we can handle before calling the functions on this.e.g. The updated
getPtr
method is:and we are getting this like this in
archive.cpp
:and will update the other code to use this approach. By using this approach we can handle the native crash for now without upgrading the minimum SDK version. If you have a better approach to not writing this check in all places, something like extension function that avoids writing this check everywhere please let me know.
In the screenshot: I have compiled the code with this new approach and tried to explicitly dispose the archive and then tried to access the content on the disposed archive and instead of crashing the program, it normally throws the exception. That we are already handling in Kiwix app.
I am not in favor of upgrading the minimum SDK to
33
because we will lose most of the devices, SDK 33 meansAndroid 13
which is one of the most recent versions of Android.