https://github.com/code-ape/lmdbrs_segfault
Example project that uses lmdb and reproduces mysterious segfault when run.
https://github.com/code-ape/lmdbrs_segfault
Last synced: 3 months ago
JSON representation
Example project that uses lmdb and reproduces mysterious segfault when run.
- Host: GitHub
- URL: https://github.com/code-ape/lmdbrs_segfault
- Owner: code-ape
- License: mit
- Created: 2016-02-21T19:50:29.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2016-02-21T21:52:52.000Z (over 10 years ago)
- Last Synced: 2024-12-31T06:43:50.162Z (over 1 year ago)
- Language: Rust
- Size: 4.88 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# lmdbrs segfault
Example project that uses lmdb and reproduces mysterious segfault when run.
I've encountered a rather bizarre segfault occurrence that is somehow linked to [lmdb-rs](https://github.com/vhbit/lmdb-rs) by [vhbit](https://github.com/vhbit). The segfault is odd and manifests in strangle places. In my project that I currently am experiencing issues with this it generally manifests when trying to transform data read from the db or move an `Arc` to the environment into a new thread. You can [check out the code here](https://github.com/code-ape/ComposeDB/tree/issue_06).
I created this repository purely for reference in helping solve this issue, which I have filed an issue for [here](https://github.com/vhbit/lmdb-rs/issues/29).