Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need a consistent way to free memory allocated in the DBMS and passed into the provider #41

Open
denis-protivensky opened this issue Jun 3, 2019 · 1 comment

Comments

@denis-protivensky
Copy link

denis-protivensky commented Jun 3, 2019

The sst_request_cb requires allocating memory for sst_req in the DBMS, but the memory is freed in the provider. If the DBMS is built with custom allocator, it leads to malloc/free allocator mismatch and therefore to an undefined behavior.

@ayurchen
Copy link
Member

ayurchen commented Jun 4, 2019

The only way I see around it is to provide a "free" callback to the provider. But its ugly and does not address the real problem: application and library are using different allocators. If there is a reason for the application to "overload" the standard malloc() call, then. apparently, the libraries that it is using should use the same allocator as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants