SIGSEGV crash in background thread T1_TbltTblUp0 when starting seekdb server in Android emulator
Open
Nobody has claimed this yet.
dima
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 339
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Description
When starting the seekdb server in an Android emulator, the process crashes with a SIGSEGV (sig_addr=0) in the background thread named T1_TbltTblUp0.
Steps to Reproduce
- Clone the repository:
git clone -b master https://github.com/oceanbase/seekdb.git - Build for Android:
./build.sh release --android --init - Navigate to the build directory:
cd build_androi...
Environment
- Platform: Android Emulator
- Repository Branch: master
- Build Command:
./build.sh release --android --init - Crash Details: SIGSEGV (sig_addr=0) in thread
T1_TbltTblUp0
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 the crash with ./build.sh release --android --init in the Android emulator and capture the SIGSEGV stack for thread T1_TbltTblUp0. Trace the null address through the seekdb server's Android build; done means the server starts without this background-thread crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp
- Domain
- backend, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100