Arch Linux

Zzipo

Member

From: North Spain

Registered: 2013-01-07

Posts: 61

Valgrind fails when using helgrind (undefined symbol)

Creating the most basic program:

    int main(){ return 1; }

Compiling it:

    g++ -std=c++17 test.c -o test.out

And trying to run helgrind:

    valgrind --tool=helgrind ./test.out

    ==5269== Helgrind, a thread error detector
    ==5269== Copyright (C) 2007-2017, and GNU GPL'd, by OpenWorks LLP et al.
    ==5269== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
    ==5269== Command: ./test.out
    ==5269==
    ./test.out: symbol lookup error: /usr/lib/valgrind/vgpreload_helgrind-amd64-linux.so: undefined symbol: pthread_mutexattr_gettype
    ==5269==
    ==5269== For counts of detected and suppressed errors, rerun with: -v
    ==5269== Use --history-level=approx or =none to gain increased speed, at
    ==5269== the cost of reduced accuracy of conflicting-access information
    ==5269== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

My system: completely updated to the latest version. Apart from the kernel, that is 4.10.13-1.

    Linux station 4.10.13-1-ARCH #1 SMP PREEMPT Thu Apr 27 12:15:09 CEST 2017 x86_64 GNU/Linux
    
    local/glibc 2.26-6 (base)
        GNU C Library
    
    local/valgrind 3.13.0-3
        A tool to help find memory-management problems in programs
    
    ldd valgrind
            linux-vdso.so.1 (0x00007ffd577c5000)
            libc.so.6 => /usr/lib/libc.so.6 (0x00007f538e16b000)
            /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x000055f1d6602000)

Why? Can you reproduce this behavior?