https://bugs.kde.org/show_bug.cgi?id=509666
Aliaksei Kandratsenka <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #9 from Aliaksei Kandratsenka <[email protected]> --- Hi. I am gperftools maintainer. We should perhaps coordinate what is the intended behavior here. The code that gets into infinite loop explicitly does tc_free and tc_malloc because it assumes it will call _our_ code. The expectation is if whoever is overriding memory allocation APIs they'll have malloc/free etc, but not tc_XYZ functions. I am wondering why valgrind etc isn't "simply" doing that. I.e. have linker "find" malloc and other functions where you need them to be as opposed to using code rewriting magic. Depending on the logic here we can further establish what fixes (if any) need to be done to gperftools. -- You are receiving this mail because: You are watching all bug changes.
