https://bugs.kde.org/show_bug.cgi?id=487296
--- Comment #1 from Mark Wielaard <m...@klomp.org> --- Nice. Thanks for catching this. Yeah, it makes sense to start "tracking" std fds once they are closed (and reopened). One thought I had was that maybe this shouldn't be special cased for just stdin/out/err (0,1,2). It seems to me that those are just a special case of inherited file descriptors. Currently out testcases themselves "cheat". We have some special CLOSE_INHERITED_FDS macro in there to shut valgrind --track-fds up about any file descriptors the tests might inherit (some versions of perl "leak" them in out testsuite). We could track those, together with 0, 1, 2 through VG_(init_preopened_fds) at program startup. -- You are receiving this mail because: You are watching all bug changes.
