ldd and untrusted code

man ldd says:

[…] you should never employ ldd on an untrusted executable, since this may result in the execution of arbitrary code.

This also works

LD_TRACE_LOADED_OBJECTS=1 ld /bin/ls
	linux-vdso.so.1 (0x00007ffc3779a000)
	libbfd-2.35.2-system.so => /lib/x86_64-linux-gnu/libbfd-2.35.2-system.so (0x00007f79de56c000)
	libctf.so.0 => /lib/x86_64-linux-gnu/libctf.so.0 (0x00007f79de54b000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f79de545000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f79de371000)
	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f79de354000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f79de6f5000)