Container Overflow when calling DuckDB constructor about duckdb HOT 3 OPEN

Thanks for the report! I suspect this has to do with the way that DuckDB is built/linked. Can you make sure the header that you are using belongs to the library you are linking against (i.e. the versions are identical)? Using the header of one version of the library together with the shared object of another can cause all manners of undefined behavior.

from duckdb.

I thought about a false positive, too, but I could not justify, why it might be one.

The versions must be the same. I used CPM (https://github.com/cpm-cmake/CPM.cmake) to add the sources as a sub-module and compiled all the code with the same CMake settings. So I am 99% sure, that the versions of headers and libraries match.

from duckdb.

Perhaps you have DuckDB in your include path elsewhere and it's grabbing the wrong header?

Could you provide a full set-up script that triggers the error, including your build process?

I don't really see how this can be anything other than a header mismatch or something funky happening in the build process. The address sanitizer reports an out-of-bounds on a concatenation of two std::strings, which is not possible when running C++ code normally.

from duckdb.