Originally posted by sdack
View Post
1.) If you are developing C/C++ code, jemalloc/tbbmalloc/tcmalloc can hide/resolve/fix allocations that will SIGSEGV on glibc malloc, so be sure to pass a blank preload to your run enviroment to be sure it actually works on malloc.
2.) More on 1. jemalloc and the likes can sometimes automagically fix memory leaks due the algorithm nature of memory block reusal, so again be sure to check on glibc as well or at least be freaking sure jemalloc need to be available and never fallback to glibc.
3.) Valgrind and GDB can get very angry when this is preloaded, so always verify you clean the preload variable before reporting bugs on them.(yeah been there and was no fun)
Comment