Re: [Valgrind-users] Unique log filename

2014-09-24 Thread Skarakis, Konstantinos
Hi Eliot, I really appreciate this patch. It's exactly what I was looking for. I must be doing something wrong though. When I apply the patch and try to make I get this error: m_options.c: In function âvgPlain_expand_file_nameâ: m_options.c:244: warning: assignment discards qualifiers

Re: [Valgrind-users] Unique log filename

2014-09-24 Thread Eliot Moss
On 9/24/2014 5:31 AM, Skarakis, Konstantinos wrote: I really appreciate this patch. It’s exactly what I was looking for. I must be doing something wrong though. When I apply the patch and try to “make” I get this error: m_options.c: In function âvgPlain_expand_file_nameâ: m_options.c:244:

Re: [Valgrind-users] Unique log filename

2014-09-24 Thread Eliot Moss
On 9/24/2014 7:39 AM, Eliot Moss wrote: On 9/24/2014 5:31 AM, Skarakis, Konstantinos wrote: Ok -- I decided to just give it a try in a copy of valgrind updated to svn head. The issue is that I was temporarily sticking a null character into the format string, yet the format string was declared

Re: [Valgrind-users] can't compile valgrind 3.10.0 on SuSE Linux SLES 10SP3 64bit

2014-09-24 Thread Florian Krohm
On 16.09.2014 02:27, Patrick J. LoPresti wrote: I can confirm PTRACE_GETSIGINFO and PTRACE_SETSIGINFO are present in sys/ptrace.h for all architectures (including s390) as of glibc 2.5 but not 2.4. Well, except for ia64, where they were added a little earlier (2.3). Since Valgrind does

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

2014-09-24 Thread Vallevand, Mark K
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

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

2014-09-24 Thread 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 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