On Fri, May 15, 2009 at 6:55 AM, wrote:
>
> I am using valgrind 3.4.1 to try to find a memory leak. My
> program has an initial routine which allocates a lot of memory -
> around 1 GB. When I run the program by itself it runs fine, however
> when I run it under valgrind, one of the many malloc c
In article <200905142030.18436.jsew...@acm.org>,
Julian Seward wrote:
> On Thursday 14 May 2009, Russell E. Owen wrote:
> > I'm trying to install Valgrid 3.4.1 on a shared disk in such a way that
> > all of our users can use it, though we have a mix of various flavors of
> > linux box (x86 64-bi
file says:
ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9,
dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
so it looks like everything is properly 64 bit compiled. I also
tried putting in -m64 explicitly.
Patrick
On Thu, May 14, 2009 at 07
On Fri, 2009-05-15 at 09:31 +1000, Nicholas Nethercote wrote:
> On Fri, May 15, 2009 at 4:44 AM, Ashley Pittman wrote:
> >
> > Unless it's been fixed in the last month the VPATH stuff is broken on
> > the HEAD, I posted a patch to make the basic build work last month but
> > there are remaining p
Bart Van Assche wrote:
> On Fri, May 15, 2009 at 9:33 AM, Andy Howell wrote:
>> Hello,
>>
>>I'm seeing this with 3.4.1 compiled on fedora 9.
>>
>> Just before that I see:
>>
>> ==14457== Mutex reinitialization: mutex 0x4c621a8, recursion count 0, owner
>> 0.
>> ==14457==at 0x4A0B4A4:
On Fri, May 15, 2009 at 9:33 AM, Andy Howell wrote:
> Hello,
>
> I'm seeing this with 3.4.1 compiled on fedora 9.
>
> Just before that I see:
>
> ==14457== Mutex reinitialization: mutex 0x4c621a8, recursion count 0, owner 0.
> ==14457== at 0x4A0B4A4: pthread_mutex_init (in
> /usr/lib64/v
Hello,
I'm seeing this with 3.4.1 compiled on fedora 9.
Just before that I see:
==14457== Mutex reinitialization: mutex 0x4c621a8, recursion count 0, owner 0.
==14457==at 0x4A0B4A4: pthread_mutex_init (in
/usr/lib64/valgrind/amd64-linux/vgpreload_drd.so)
==14457==by 0x546DCE: Mu
