1.19-2 segfaults on all architectures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
leveldb (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
1.19-2 segfaults on all architectures. I'm getting this from valgrind:
1: ==8494== Process terminating with default action of signal 11 (SIGSEGV)
1: ==8494== Access not within mapped region at address 0x61632F6D6F6347
1: ==8494== at 0x4EB5804: leveldb:
1: ==8494== by 0x4ECBBAF: leveldb:
1: ==8494== by 0x4ECBD87: leveldb:
1: ==8494== by 0x4ED1F8F: leveldb:
1: ==8494== by 0x4ED2113: leveldb:
1: ==8494== by 0x4EA68AB: leveldb:
1: ==8494== by 0x4EAD183: leveldb:
1: ==8494== by 0x4EAEECF: leveldb:
1: ==8494== by 0x4EAFD3F: leveldb:
1: ==8494== by 0x4EB051F: leveldb:
1: ==8494== by 0x4ED7C3B: ??? (in /usr/lib/
1: ==8494== by 0x53E901B: start_thread (pthread_
The code using leveldb has been stable for more than a year and works perfectly on vivid, xenial, and zesty. With leveldb 1.18-5, I can run the tests for days on end without any problems. The instant is install 1.19-2, I get segfaults.
See https:/
Changed in leveldb (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Confirmed |
Upstream bug here: https:/ /github. com/Level/ leveldown/ issues/ 321