Is this a bug in ld-elf.so.2?
While debugging an error in evolution-2.8, I ran across this odd-
looking error message in gdb:
0x2806b445 1667 strncpy(pathname, dir, dirlen);
src=0x1a <Error reading address 0x1a: Bad address>, n=3217027296)
The line 1667 in question is at /usr/src/libexec/rtld-elf/rtld.c:1667
and the program continues past that error as if nothing had gone
wrong. (Possibly because the return code from strncpy is never
checked? Dunno, but it worries me.)
Given a little more time and effort I may be able to find out where
the bad pointer is coming from -- but is it worth the effort? Is
this really a problem, or not?