[parsec-users] x264 run error
dvyukov at google.com
Fri Jan 3 14:38:50 EST 2014
It reports lots of uninit reads.
For valgrind to you need to compile with "-O0 -g". You seem to be
missing debug info, so memcheck does not output function names. -O0 is
critical as well.
There is an option related to "origin tracking" in memcheck, it should
produce more informative reports.
Also if you are using valgrind, hellgrind may be useful to detect data races.
On Fri, Jan 3, 2014 at 11:32 PM, Paulo Eduardo <paulocoronato at gmail.com> wrote:
> Tanks Dmitry!
> I have used the valgrind, but It don't show where is the problem at
> least I don't understood where the problem can be.
> I attach the log
> Em 03-01-2014 15:53, Dmitry Vyukov escreveu:
>> On Fri, Jan 3, 2014 at 8:38 PM, Paulo Eduardo Nogueira
>> <paulocoronato at gmail.com> wrote:
>>> Someone can help me? Every time that I run the x264 I have error below.
>>> *** Error in
>>> double free or corruption (!prev): 0x00000000011c9c00 ***
>> I would run it under AddressSanitizer/ThreadSanitizer/MemorySanitizer:
>> parsec-users mailing list
>> parsec-users at lists.cs.princeton.edu
> Paulo Eduardo Nogueira
> Professor - Instituto Federal Goiano
> HPDCS /UFU
> Phone: +55 64 92846959
> Phone: +55 16 999983161
> paulocoronato at gmail.com
> parsec-users mailing list
> parsec-users at lists.cs.princeton.edu
More information about the parsec-users