You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The
sst_request_cb
requires allocating memory forsst_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.The text was updated successfully, but these errors were encountered: