[nightlies] Crash on amd64 during test run
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
U1DB |
Fix Released
|
High
|
Samuele Pedroni |
Bug Description
The tests are currently crashing on amd64 on Ubuntu 13.10, with this stack from valgrind:
==5691== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==5691== Access not within mapped region at address 0x0
==5691== at 0xA1C1790: extract_
==5691== by 0xA1C1CFE: op_combine (u1db_query.c:499)
==5691== by 0xA1C2081: evaluate_
==5691== by 0xA1C2798: sqlite_
==5691== by 0x9B37EBF: sqlite3_exec (in /usr/lib/
==5691== by 0xA1C3E91: u1db__update_
==5691== by 0xA1BBC50: write_doc (u1db.c:483)
==5691== by 0xA1BE778: u1db_put_doc (u1db.c:689)
==5691== by 0xA1BE8C4: u1db_create_
==5691== by 0xA19DB6C: __pyx_pf_
==5691== by 0xA19D97E: __pyx_pw_
==5691== by 0x487578: PyCFunction_Call (methodobject.c:85)
==5691== If you believe this happened as a result of a stack
==5691== overflow in your program's main thread (unlikely but
==5691== possible), you can try to increase the size of the
==5691== main thread stack using the --main-stacksize= flag.
==5691== The main thread stack size used in this run was 16777216.
==5691==
Related branches
- dobey (community): Approve
-
Diff: 41 lines (+5/-4)1 file modifiedsrc/u1db_query.c (+5/-4)
Changed in u1db: | |
status: | In Progress → Fix Committed |
tags: | added: u1-by-dev u1-on-dev u1-syncdaemon |
Changed in u1db: | |
status: | Fix Committed → Fix Released |
Here is the code for a simple test case program, which exposes the crash.