Re: [Valgrind-users] Problems with valgrind after a fork() and starting a container

[Alan C. <ala...@gm...>]

hi,

Tom is right you can detach if you don't use exec but i think you can
silent child output using --child-silent-after-fork=no

Alan

2014-09-24 23:45 GMT+02:00 Tom Hughes <to...@co...>:

> On 24/09/14 22:04, Vallevand, Mark K wrote:
>
> > We don’t care about valgrind in the child process.  We need to get the
> > child to detach from valgrind before it calls the lxc library.
> >
> > So, how can this be done?
>
> It can't - valgrind is a fundamental part of the process and the only
> way to get rid of it is to exec into a different binary.
>
> Tom
>
> --
> Tom Hughes (to...@co...)
> http://compton.nu/
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>