> > In short there's a conflict between optimising the hell out of stringops > > and having enough visibility for reliable debugging. Given the above > > constraints I don't see how you can have your cake and eat it. > > Unfortunately this conflicts with using Valgrind for other useful functions > like instruction trace. If you arbitrarily substitute your own string > functions, the trace is invalid.
There is no conflict in the insn trace (etc) case. The intercepts I mention only apply to Memcheck, not to any of the other tools. J ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
