Re: [Valgrind-users] Invalid read raised with stpncpy

[Patrick J. L. <lop...@gm...>]

On Mon, Aug 13, 2012 at 8:54 AM, John Reiser <jr...@bi...> wrote:

>
> In the case at hand, we are interested in string operations, not floating
> point.
> Suppose that stpncpy contributes 0.25% (1/400) of the normal running time.
>  Then
> instruction-by-instruction emulation of stpncpy by memcheck is about 20 *
> 0.25% = 5%
> of the normal running time.


Yes, for the (approximately) one application on the planet for which (the
non-standard) stpncpy consumes 1/400 of the running time, you would be
right.  If, that is, the rest of the application were not also running 20
times slower.

Also, note that the same "argument" applies to every function in the
standard library, leading to my earlier modest proposal to add interceptors
for absolutely everything.

Since I am starting to repeat myself, I guess I am done with this
discussion.  Feel free to have the last word.

 - Pat