https://bugs.kde.org/show_bug.cgi?id=514343
Philippe Waroquiers <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |philippe.waroquiers@skynet. | |be --- Comment #2 from Philippe Waroquiers <[email protected]> --- A maybe more general alternative to a macro 'VALGRIND_REPLACES_MALLOC" would be to provide to the guest a way to interrogate which tool is currently running. Then the guest can from the tool derive the fact that MALLOC is replaced but can also do other things differently depending on the tool. For example, when running under helgrind, at work, we have here and there some specific logic. Or yet another more extensible alternative: a "general" macro VALGRIND_GET_PROPERTY that would have an argument property_id with some constants defined in valgrind.h such as: TOOL (to get the name of the tool), REPLACES_MALLOC (returning if the current tool is replacing malloc); etc. -- You are receiving this mail because: You are watching all bug changes.
