SIGSEGV crash when accessing system virtual table oceanbase.__all_virtual_thread during seekdb startup on Android arm64
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 339
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Description
A segmentation fault (SIGSEGV) occurs when the seekdb process accesses the system virtual table oceanbase.__all_virtual_thread during its startup sequence on an Android arm64 environment.
Actual Result
After the environment starts and prints normal initialization logs, an internal SQL query is executed against oceanbase.__all_virtual_thread. This causes the process to trigger a signal 11 (SIGSEGV), resulting in a "Segmentation fault" message on the console.
Steps to Reproduce
Start the seekdb process in an Android arm64 environment.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing seekdb startup on Android arm64 and capture the stack trace around the internal query against oceanbase.__all_virtual_thread. Trace the startup path and virtual-table access involved; done means startup completes without a signal 11 crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp
- Domain
- databases, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100