-
Notifications
You must be signed in to change notification settings - Fork 568
Crash: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x54 #508
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
Comments
Hi @aeroxr1
SQLCipher for Android |
Sorry, the pragma version was wrong ignore it. |
Hi @aeroxr1 Can you post the test scenario? Also, can you provide a Java stack trace associated with the crash of the test? More information about the scenario is needed to help debug further. |
The db i'm using is json1 without password. A specific query is causing the crash in some cases for example on production db and not on dev db.
|
Seems the crash is related to a CAST. |
Hi @aeroxr1 I put together the following test which is successful within the SQLCipher for Android test suite using both
|
Hi, tomorrow I will continue to investigate. |
Ok, Is there a way I can share with you my db with my test query? Thanks for the support |
Hello @aeroxr1 You can fork the SQLCipher for Android test suite, create a sample reproduction case following these instructions, push up your changes, and then provide the URL to your repository for review. Would you give that a try? Thanks! |
Hi ! Thanks I'm working on it :) |
Ok, |
Hello @aeroxr1 This issue is not isolated to SQLCipher specifically, I have verified it also fails from the SQLite command line shell using version 3.31.0. You may wish to report this to the upstream SQLite team for further information. Additionally, I was able to capture the crash in SQLite 3.31.0 using
Also, this was the following backtrace from that query execution:
I am going to close this issue as it is not specific to SQLCipher for Android. Thanks! |
So you don't know if this could be something wrong with my db/query or a sqllite bug? |
Hi @aeroxr1 Because it is causing a crash in standard SQLite, it would be best to report it upstream to get their feedback. Good luck! |
@developernotes would you mind giving me some instructions how to reproduce this on SQLite 3.31.0? I would love to see this crash fixed upstream, and would love to help see this happen, would be easier if I don't have to build the custom test app. |
Hi @brodybits You must build SQLite with JSON support (i.e.,
|
https://github.com/aeroxr1/sqlcipher-android-tests/blob/master/app/src/main/assets/dbTest.db Does not crash for me on the most recent snapshot from https://www.sqlite.org/download.html. I will try with SQLite 3.31.1 next. |
I do see a crash on SQLite 3.31.1 but as I said before, no crash on the most recent snapshot. I do hope they will release a patch of SQLite in the near future. In case this is an urgent issue, it is possible though potentially risky to patch SQLCipher yourself: https://discuss.zetetic.net/t/sqlcipher-sqlite-update/2470/11 |
Hi @brodybits , thanks for you help. Have you found which bug fix is related to this crash? It would be helpful to have a reference so that I could search for other potentially dangerous queries in my code. Do you think that I can modify in some way the query to avoid the bug and obtain the same results? Thank you both for your support. |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
i'm having the following crash:
I'm able to reproduce the crash on the testSuite both with last library version 4.3.0 and 4.2.0 (the version that I'm currently using on my app)
Can you help me ?
The text was updated successfully, but these errors were encountered: