When doing a client-side durable upsert in python, only when I've made the kv_tracing_threshold low enough, I get a segfault:
the first frame - note that node->next = iter->cur:
So - seems the node is maybe pointing to uninitialized memory? I don't believe we manipulate these spans (the pointers are opaque to us), so I'd suspect the issue is in LCB. LMK what you think.
Environment
None
Gerrit Reviews
None
Release Notes Description
None
Activity
Show:
CB robot September 15, 2020 at 11:05 AM
Build couchbase-server-7.0.0-3115 contains libcouchbase commit 7032b94 with commit message: Intermittent segfault in client durable store
David Kelly May 7, 2020 at 2:26 PM
Similar to the issue in , except that was strictly for the {{lcb_exists}} calls. Looking at this now, hoping to see something similar...
Fixed
Pinned fields
Click on the next to a field label to start pinning.
When doing a client-side durable upsert in python, only when I've made the kv_tracing_threshold low enough, I get a segfault:
the first frame - note that
node->next = iter->cur:So - seems the node is maybe pointing to uninitialized memory? I don't believe we manipulate these spans (the pointers are opaque to us), so I'd suspect the issue is in LCB. LMK what you think.