tact the sender and delete the e-mail and its
> attachments from all computers.
> From: Alan Copy [mailto:alan.c...@gmail.com]
> Sent: Thursday, September 25, 2014 06:51 AM
> To: Tom Hughes
> Cc: Vallevand, Mark K; valgrind-users@lists.sourceforge.net
> Subject: Re: [Valgrind-users]
computers.
From: Alan Copy [mailto:alan.c...@gmail.com]
Sent: Thursday, September 25, 2014 06:51 AM
To: Tom Hughes
Cc: Vallevand, Mark K; valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] Problems with valgrind after a fork() and
starting a container
hi,
Tom is right you can det
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 :
> On 24/09/14 22:04, Vallevand, Mark K wrote:
>
> > We don’t care about valgrind in the child process. We need to get th
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
In our program, we do a fork() and in the child process the lxc library is
called to start a container. The child process does not call exec().
Valgrind and lxc do not play nicely, at least with the versions in Ubuntu 12.04
LTS.
We don't care about valgrind in the child process. We need to get
