Hi Benjamin,
> thanks for your support. I installed the packages valgrind-dbg, libc6-l10n
> and locales
> so that we can compare our systems. But the problem is still present.
> I attached a file with my debugging output.
Looks quite equal, except kernel and cpu.
Maybe the commands below can reveal any difference?
Kind regards,
Bernhard
# From a VM running current buster with valgrind not showing a problem:
root@debian:~# ls -lisah /lib/ld-linux-armhf.so.3
/lib/arm-linux-gnueabihf/ld-linux-armhf.so.3
/lib/arm-linux-gnueabihf/ld-2.28.so /lib/arm-linux-gnueabihf/ld-2.28.so
787943 104K -rwxr-xr-x 1 root root 104K Feb 28 06:56
/lib/arm-linux-gnueabihf/ld-2.28.so
787943 104K -rwxr-xr-x 1 root root 104K Feb 28 06:56
/lib/arm-linux-gnueabihf/ld-2.28.so
789695 0 lrwxrwxrwx 1 root root 10 Feb 28 06:56
/lib/arm-linux-gnueabihf/ld-linux-armhf.so.3 -> ld-2.28.so
789740 0 lrwxrwxrwx 1 root root 30 Feb 28 06:56 /lib/ld-linux-armhf.so.3
-> arm-linux-gnueabihf/ld-2.28.so
root@debian:~# md5sum /lib/ld-linux-armhf.so.3
/lib/arm-linux-gnueabihf/ld-linux-armhf.so.3
/lib/arm-linux-gnueabihf/ld-2.28.so /lib/arm-linux-gnueabihf/ld-2.28.so
a4b6b7a988547a464b0c57a74b32f9c4 /lib/ld-linux-armhf.so.3
a4b6b7a988547a464b0c57a74b32f9c4 /lib/arm-linux-gnueabihf/ld-linux-armhf.so.3
a4b6b7a988547a464b0c57a74b32f9c4 /lib/arm-linux-gnueabihf/ld-2.28.so
a4b6b7a988547a464b0c57a74b32f9c4 /lib/arm-linux-gnueabihf/ld-2.28.so
root@debian:~# gdb -q -ex 'b index' -ex 'q' --args
/lib/arm-linux-gnueabihf/ld-2.28.so
Reading symbols from /lib/arm-linux-gnueabihf/ld-2.28.so...Reading symbols from
/usr/lib/debug/.build-id/3c/95192f00377a31cf9a97cdbfe02020846ca790.debug...done.
done.
Breakpoint 1 at 0x12090: file ../sysdeps/arm/armv6/strchr.S, line 28.
root@debian:~# strace -f valgrind /bin/true 2>&1 | grep ld-linux-armhf.so.3
pread64(3, "/lib/ld-linux-armhf.so.3\0", 25, 340) = 25
open("/lib/ld-linux-armhf.so.3", O_RDONLY) = 4
