Menu
▾
▴
valgrind-users
|
From: Vallevand, M. K <Mar...@UN...> - 2014-09-24 21:23:58
|
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 the child to detach from valgrind before it calls the lxc library. So, how can this be done? Any suggestions will be welcome. And, thanks! Regards. Mark K Vallevand "If there are no dogs in Heaven, then when I die I want to go where they went." -Will Rogers THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. |
|
From: Tom H. <to...@co...> - 2014-09-24 21:45:26
|
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/ |
|
From: Alan C. <ala...@gm...> - 2014-09-25 11:50:56
|
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 > |
|
From: Vallevand, M. K <Mar...@UN...> - 2014-09-25 13:17:09
|
I tried that option. Doesn’t help. I was afraid that it would be what Tom said. [Theatrical sigh] I have a couple of choices, I guess. Find out why valgrind and lxc aren’t working together and fix that. Or, do some kind of exec() outside of lxc. The lxc_start() that is being called is a kind of exec(), I guess. It creates a new set of namespaces and does a clone() and exec() in them. That is where is it failing. I’m trying to get a log file with more details. There might be a chance to figure this out. Regards. Mark K Vallevand "If there are no dogs in Heaven, then when I die I want to go where they went." -Will Rogers THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. From: Alan Copy [mailto:ala...@gm...] Sent: Thursday, September 25, 2014 06:51 AM To: Tom Hughes Cc: Vallevand, Mark K; val...@li... Subject: Re: [Valgrind-users] Problems with valgrind after a fork() and starting a container 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...<mailto: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...<mailto: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...<mailto:Val...@li...> https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Julian S. <js...@ac...> - 2014-09-26 16:36:55
|
Yes, if you get some details on how/why it fails, that would be good. Also, filing a bug in bugzilla (see http://www.valgrind.org/support/bug_reports.html) will ensure your bug report doesn't get lost later on. J On 09/25/2014 02:58 PM, Vallevand, Mark K wrote: > I tried that option. Doesn’t help. > I was afraid that it would be what Tom said. [Theatrical sigh] > I have a couple of choices, I guess. Find out why valgrind and lxc aren’t working together and fix that. Or, do some kind of exec() outside of lxc. > The lxc_start() that is being called is a kind of exec(), I guess. It creates a new set of namespaces and does a clone() and exec() in them. That is where is it failing. I’m trying to get a log file with more details. There might be a chance to figure this out. > > Regards. > Mark K Vallevand > "If there are no dogs in Heaven, then when I die I want to go where they went." > -Will Rogers > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. > From: Alan Copy [mailto:ala...@gm...] > Sent: Thursday, September 25, 2014 06:51 AM > To: Tom Hughes > Cc: Vallevand, Mark K; val...@li... > Subject: Re: [Valgrind-users] Problems with valgrind after a fork() and starting a container > > 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...<mailto: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...<mailto: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...<mailto:Val...@li...> > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > > > ------------------------------------------------------------------------------ > 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 > |
Thanks for helping keep SourceForge clean.
X