Nominate our 2022 Qt Champions!

Valgrind stops with external error

  • I am running Qt Creator 4.10.1 in Linux Mint 18.3. I get the following external error with the "Valgrind Memory Analyzer" and my "Qt Widgets Application" stops suddenly:

    286,959 bytes in 1 blocks are possibly lost in loss record 78 of 78
      in calloc in /usr/lib/valgrind/
      1: calloc in /usr/lib/valgrind/
      2: /usr/lib/nvidia-384/
      3: /usr/lib/nvidia-384/
      4: /usr/lib/nvidia-384/
      5: /usr/lib/nvidia-384/
      6: /usr/lib/nvidia-384/
      7: /usr/lib/nvidia-384/
      8: call_init.part.0 in /build/glibc-LK5gWL/glibc-2.23/elf/dl-init.c:58
      9: call_init in /build/glibc-LK5gWL/glibc-2.23/elf/dl-init.c:30
      10: _dl_init in /build/glibc-LK5gWL/glibc-2.23/elf/dl-init.c:120
      11: /lib/x86_64-linux-gnu/

    My project is of "Desktop Qt 5.12.5 GCC 64bit" type.

    Note: I get the same problem with fresh "Qt Widgets Application" (I don't see how you can change it to a regular "Desktop" type).

    I can't open "dl-init.c", but I'm guessing I shouldn't touch it?

    Is it something to do with my video card?

    Can I suppress the error and continue the analysis?


  • Lifetime Qt Champion

    @Guerrian Without Valgrind your app is not crashing?
    Do you see any other output (warnings/errors) when your app stops?

  • @jsulm Yes, exactly. No other warnings / errors.

    11:28:07: valgrind --child-silent-after-fork=yes --xml-socket= --log-socket=
    --xml=yes --smc-check=stack --tool=memcheck --gen-suppressions=all --track-origins=yes --leak-check=summary --num-callers=25
    11:28:13: The program has unexpectedly finished.
    11:28:13: Process exited with return value Process crashed
    11:28:13: Analyzing finished.

    It's just a blank "Qt Widgets Application".

    If I run the program normally (i.e. without Valgrind) and close the window then I get this message:

    17:07:32: Starting /home/daniel/Documents/QtNew/build-TestWidgets-Desktop_Qt_5_12_5_GCC_64bit-Debug/TestWidgets ...
    QApplication: invalid style override passed, ignoring it.
        Available styles: Windows, Fusion
    17:07:48: /home/daniel/Documents/QtNew/build-TestWidgets-Desktop_Qt_5_12_5_GCC_64bit-Debug/TestWidgets exited with code 0

    Getting rid of this "invalid style" message does not fix the original problem!

  • @jsulm I upgraded Valgrind from source to version "3.15.0" and the crash problem went away.

Log in to reply