(4) ==3737== Open AF_INET socket 3: 127.0.0.1:45266 <-> 127.0.0.1:1500 (4) ==3737== <inherited from parent> it appears that valgrind doesn't set CLOEXEC on the log socket. also a way to suppress open fds would be nice as I end up with connections to my ldap server in the list as well (from nss_ldap or similar I assume).
If you're using --trace-children=yes you don't want it to close-on-exec as you want it to continue logging as you trace the execed process. I suspect this is really a variant of bug 140939 except that you have a logging descriptor that isn't stderr which means the patch on that bug probably needs enhancing to ignore the logging descriptor as well.
depends on if a new socket is opened after exec I suspect it is as the connection count goes up.
also should verify that its the controlling terminal if possible but not sure how or if this is possible
(In reply to comment #3) > also should verify that its the controlling terminal if possible but not sure > how or if this is possible ops wrong bug
This seems a different variant of https://bugs.kde.org/show_bug.cgi?id=311655 but with --log-socket= instead of --log-file= See also bug 488379
commit fbd7596f8342f0b0fbbe088d960da839a8bdb839 Author: Mark Wielaard <mark@klomp.org> Date: Sun Jun 16 21:23:08 2024 +0200 Don't leave fds created with --log-file, --xml-file or --log-socket open prepare_sink_fd and prepare_sink_socket will create a new file descriptor for the output sink. finalize_sink_fd then copies the fd to the safe range, so it doesn't conflict with any application fds. If we created the original fd ourselves, it was a VgLogTo_File or VgLogTo_Socket, not VgLogTo_Fd, finalize_sink_fd should close it. Also close socket when connecting fails in VG_(connect_via_socket). Add a testcase for --log-file and --xml-file which prints output to /dev/stderr https://bugs.kde.org/show_bug.cgi?id=202770 https://bugs.kde.org/show_bug.cgi?id=311655 https://bugs.kde.org/show_bug.cgi?id=488379 Co-authored-by: Alexandra Hájková <ahajkova@redhat.com