>> I thought anything in a pub_tool_* header was available to tools? > >Yeah .. it is. I'm not exactly clear about the architectural rationale >of having a formal core-tool interface >(include/pub_tool_tooliface.h) and >also a bunch of functions (include/pub_tool_everythingelse.h). There's >probably a good reason, but I don't know what it is.
I understand that pub_tool_tooliface.h is what allows the tool to give some of "its tool" functions/data to the core, so that the core receive the needed tool functions it must know about. While all the other pub_tool_everythingelse.h is what the tool can call itself directly from the core. But I did not check exhaustively pub_tool_tooliface.h to see it is only made of such "give something to the core so core can call the tool". Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
