Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COCan you explain how to properly hide the symbols, and what you're saying about the memory operations? We tried wrapping the 3rd party lib in functions that would use dlopen(lib, RTLD_LOCAL) to load the 3rd party lib. This kept our code from linking in .so.5, but, we suspected, that the 3rd party code was picking up symbols (like malloc) from the already loaded .so.6 (loaded by our code), and was causing memory leaks. We tried using LD_PRELOAD to loud the 3rdparty lib first, and the memory leaks pretty much went away.
      singulars
    2. COAnd we _do_ allocate in on our side, and the 3rd party lib deallocates. e.g.: ThirdPartyStruct * foo = malloc(...); ThirdPartyApiCall(foo); ThirdPartyFreeStruct(foo); - Are you saying that just plain won't be possible if we're using .6, and its using .5? What if we used .5 with our wrapper functions, and did all allocation/deallocation through the wrapper lib?
      singulars
    3. COWhen allocation/deallocaiton is performed in different standard libraries you cannot be sure that they do this in same way... you simply do not knoww. I can't say if it is a real problem on Linux but on Windows definitely it is: if you are using different runtimes in your libraries and do allocation in one and deallocation in other you will get a run-time exception. I wouldn't even consider mixing different standard libraries in your case, even if it works on this particular platform with these particular runtimes you cannot be sure it will work when you move to a new version of libstd...
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload