Comment 9 for bug 1247026

> After a lot of investigations I came up with conclusion, that strlen
> shouldn't be looked at by valgrind at all, as this causes more trouble than
> it's worth, as evident not only by this bug, but by false-positives like
> https://bugzilla.redhat.com/show_bug.cgi?id=678518

That bug is completely unrelated to this one. Red herring.

The requirement for intercepting strlen in ld.so was to avoid lots of
false positives from Memcheck at startup. I believe it is still
necessary, and you haven't produced any evidence in to the contrary:
you don't show any results from your investigations.