Hi,
> There may be a bug in valgrind 3.1.0 which has been fixed; the current
> release is 3.11.0. Can you compile or download binaries for version 3.11.0?
I tried Valgrind 3.10.0 and get the same error as with 3.1.0
> If it still fails (or if you can't use a copy of 3.11.0), the next step is
>
On 11/16/2015 8:06 AM, Jan Kubalek wrote:
> Hello,
>> What happens if you compile without "-static"? Valgrind wants to replace
>> system libraries with its own versions so that it can trace memory
>> allocation and release. It does so at runtime, so static linking is not
>> good for it.
> If I co
Hello,
> What happens if you compile without "-static"? Valgrind wants to replace
> system libraries with its own versions so that it can trace memory
> allocation and release. It does so at runtime, so static linking is not
> good for it.
If I compile program without "-static"
gcc -gdwarf-
On 11/13/2015 10:54 AM, Jan Kubalek wrote:
> Hi :),
>
> I have a prog. with pthread semaphores. Everything works fine, but i
> have a small problem with valgring.
>
> If I commpile my program with
> gcc -gdwarf-2 -O0 -static main.c -lpthread
> and run as
> valgrind --tool=helgrind --read-
Hi :),
I have a prog. with pthread semaphores. Everything works fine, but i
have a small problem with valgring.
If I commpile my program with
gcc -gdwarf-2 -O0 -static main.c -lpthread
and run as
valgrind --tool=helgrind --read-var-info=yes ./a.out
I get
==15757== Process terminating with
