libpmemobj-cpp
libpmemobj-cpp copied to clipboard
pmem
C++ bindings & containers for libpmemobj
Currently, persistent vector, array and string are not allowed on volatile memory (including stack). This makes it impossible to pass/return those containers by value. This limitation was introduced to decrease...
Currently only way to check if some feature (for example hashmap) is present is to try to compile some example code. We could put: `#define FEATURE_NAME_PRESENT 1` in version.hpp file.
1st thread: * start thread * acquire accessor with write lock to element * insert element * start 2nd thread * wait for semaphore * check element (should be value...
# ISSUE: cond_var_posix_0_helgrind ## Environment Information - libpmemobj-cpp version(s): - PMDK (libpmemobj) package version(s): - OS(es) version(s): - kernel version(s): - compiler, libraries, packaging and other related tools version(s): and...
Currently, we do not test that containers do not leak any memory. We could use POBJ_FOREACH after each test to verify that only root object is allocated. This would require...
It is not possible to support cross-pool swap in concurrent_hash_map and in concurrent_skip_list because we do not support cross-pool transactions.
``` 18/58 Test #20: cond_var_0_none ...................................................***Failed 1.73 sec -- Executing: C:/projects/libpmemobj-cpp/build/tests/Release/cond_var.exe C:/projects/libpmemobj-cpp/build/test/cond_var_0_none/testfile -- Stdout: Signal 22, backtrace: 11: [00007FF72D716BE6] 10: [00007FF72D716D3B] 9: raise [00007FFC0A19DC17] 8: abort [00007FFC0A19EAA1] 7: [00007FF72D7128BD] 6:...
