3 ms·
It really sucks to have to change code so much to do the analysis. I guess it's a simple change that can be automated but ugh...
by wakawaka28 2y ago
It really sucks to have to change code so much to do the analysis. I guess it's a simple change that can be automated but ugh...
- PaulDavisThe1st 2y agooperator->, operator= and the copy constructor(s) are in the hot path for std::*_ptr ... you do not want them cluttered with debugging code ... until you do.
- wakawaka28 2y agoI'm talking about having to change existing code to use the library, to enable the analysis. I don't want to do that. I don't care much how they make it happen... Ideally, it could be done with `LD_PRELOAD` tricks but that won't work because of the templated nature of smart pointers.
- PaulDavisThe1st 2y agowhen we hacked boost::*_ptr to do this, we used an environment variable to turn on the types we wanted traced. there would have no point in tracing every type that was managed with smart pointers, so there has to be at least 1 line of code modification just to identify what you wanted traced.