libpmemobj-cpp icon indicating copy to clipboard operation
libpmemobj-cpp copied to clipboard

C++ bindings & containers for libpmemobj

Results 85 libpmemobj-cpp issues
Sort by recently updated
recently updated
newest added

It happend on Travis, once (TYPE=normal OS=ubuntu OS_VER=18.04 PUSH_IMAGE=1) ```sh PKG_CONFIG_PATH=/opt/pmdk/lib/pkgconfig/ \ CC=gcc CXX=g++ \ cmake .. -DDEVELOPER_MODE=1 \ -DCMAKE_BUILD_TYPE=Debug \ -DCMAKE_INSTALL_PREFIX=$INSTALL_DIR \ -DTRACE_TESTS=1 \ -DCOVERAGE=$COVERAGE make -j2 test_command tests_gcc_debug...

Type: Bug
Priority: 3 medium

These examples should be tested regularly: - array - map_cli - panaconda

Type: Bug
Type: Feature
validation
Priority: 2 high

Only $(PKG)_INCLUDEDIR and $(PKG)_INCLUDE_DIRS exist, but many CMakeFiles in libpmemobj-cpp use $(PKG)_INCLUDE_DIR. See https://cmake.org/cmake/help/v3.6/module/FindPkgConfig.html#command:pkg_check_modules

Type: Bug
Priority: 4 low

To guarantee correctness function passed to C as callback should have C linkage (define in extern "C"). This is not the case here. Current behavior can cause errors in some...

Type: Bug
Priority: 3 medium

While compiling I'm getting an error: ```Package 'libpmemobj', required by 'virtual:world', not found``` Even though `libpmeobj` package is installed. After installing `libpmemobj-devel` package, error disappears :) OS: Fedora 29 libpmemobj++:...

Type: Bug
Priority: 4 low

Debian unstable: gcc-9, valgrind 3.15 Full log from two official buildds: [x86-ubc-01](https://buildd.debian.org/status/fetch.php?pkg=libpmemobj-cpp&arch=amd64&ver=1.8-1&stamp=1570124972&raw=0), [x86-csail-02](https://buildd.debian.org/status/fetch.php?pkg=libpmemobj-cpp&arch=all&ver=1.8-1&stamp=1570125012&raw=0). ``` 48/957 Test #163: concurrent_hash_map_rehash_0_helgrind ..................................................................................***Failed 5.29 sec -- Executing: valgrind --error-exitcode=99 --tool=helgrind //obj-x86_64-linux-gnu/tests/concurrent_hash_map_rehash //obj-x86_64-linux-gnu/test/concurrent_hash_map_rehash_0_helgrind/testfile -- Test...

Type: Bug
Priority: 4 low

One solution is to call free_data() in delete_persistent method. This will allow to propagate exception and not abort application (if throwed inside destructor). All containers should implement this method. Another...

Type: Bug
Type: Feature
Priority: 3 medium

# Problem Right now, after destroying an object (but not freeing it) memory is in initialized state. In case of vector this is problematic for methods like clear() (which destroy...

Type: Bug
Type: Feature
Priority: 3 medium

# ISSUE: concurrent_map_insert_reopen_0_drd random failure ## Environment Information - libpmemobj-cpp version(s): 1.10-rc1 ## Actual behavior: ## Details Some annotations are used in ctors which are not called during reopen. Hence...

Type: Bug
concurrent_map
Priority: 4 low

Using the following results in no data in LIBPMEMOBJ++_INCLUDE_DIRS ```cmake pkg_check_modules(LIBPMEMOBJ++ REQUIRED libpmemobj++>=${LIBPMEMOBJ_CPP_REQUIRED_VERSION}) message (STATUS "LIBPMEMOBJ++_INCLUDE_DIRS = ${LIBPMEMOBJ++_INCLUDE_DIRS}") message (STATUS "LIBPMEMOBJ++_LIBRARIES = ${LIBPMEMOBJ++_LIBRARIES} ") ``` ## Environment Information - libpmemobj-cpp...

Type: Bug
Priority: 3 medium