> Valgrind meet containers. > > Containers meet valgrind. Unless the container implementation has a way to "whitelist" some open fd then the container mechanism is to blame for not providing functionality that is reasonably required for debugging.
If the container mechanism does have such a "fd whitelist" then *you* should figure out how valgrind can use it, and submit the patches (or documentation, strategy, etc.) to valgrind. Either way, please visit https://bugs.kde.org/enter_bug.cgi?product=valgrind and enter a report so that the issue does not get lost. Specify which container environment, etc. Give enough details so that somebody else can reproduce your observations starting "from scratch". Then in the short run, the container mechanism probably has the attitude "I provide an encapsulated, protected environment for running ["mature"] programs", so you should run valgrind in an environment that is more friendly to debugging. [Get another x86_64 computer and run Linux on it.] ------------------------------------------------------------------------------ Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
