codesite-nore...@google.com

Comment #2 on issue 152 by donavanbadboy: Does tcmalloc use recursion?  
(Stack overflow with fragmented memory suspected)
http://code.google.com/p/google-perftools/issues/detail?id=152

Hi,

I think I've tracked it down. The problem was in a seemingly completely  
unrelated
external dynamically linked library. First of all, I found a case where the  
heap
corruption was repeatable, I then started taking bits of code out  
trial-and-error
style to see what was causing the problem.

It turns out that linking with *name deleted to save embarresment*'s  
anti-virus API,
caused heap corruption in such a way that later down the line either glibc's
malloc/free or tcmalloc's crashed a burnt.

There must be something in this libraries init() function causing memory  
(probably in
the heap) corruption showhow, as I don't even need to call any of this API's
functions, just link with it at compile time and obviously include function  
calls in
the code to make it actually link properly.

Sorry for the red herring, and keep up the good work!

Regards, Dan....

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings