Databases
StackOverflow2013
Postsdbo
POIs anyone using valgrind and Qt?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs anyone using valgrind and Qt?
    primarykey
    data
    text
    <p>I am trying to debug a large application build using Qt/C++ and valgrind is reporting a lot of memory leak from internal Qt stuff. Could anyone share a proper valgrind suppression file for Qt apps ?</p> <p>Thanks !</p> <p>Eg.</p> <pre><code>#include &lt;qobject.h&gt; int main() { QObject o; return 0; } </code></pre> <p>returns:</p> <pre> $ valgrind --leak-check=full --show-reachable=yes ./leak ==12655== Memcheck, a memory error detector ==12655== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==12655== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright info ==12655== Command: ./leak ==12655== ==12655== ==12655== HEAP SUMMARY: ==12655== in use at exit: 744 bytes in 7 blocks ==12655== total heap usage: 28 allocs, 21 frees, 1,640 bytes allocated ==12655== ==12655== 16 bytes in 1 blocks are still reachable in loss record 1 of 7 ==12655== at 0x4C229C7: operator new(unsigned long) (vg_replace_malloc.c:220) ==12655== by 0x6203124: QThreadData::current() (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x62FC4BC: QObject::QObject(QObject*) (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x4008D2: main (in /tmp/Qt/bin/leak) ==12655== ==12655== 96 bytes in 1 blocks are still reachable in loss record 2 of 7 ==12655== at 0x4C229C7: operator new(unsigned long) (vg_replace_malloc.c:220) ==12655== by 0x62030FC: QThreadData::current() (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x62FC4BC: QObject::QObject(QObject*) (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x4008D2: main (in /tmp/Qt/bin/leak) ==12655== ==12655== 96 bytes in 1 blocks are still reachable in loss record 3 of 7 ==12655== at 0x4C229C7: operator new(unsigned long) (vg_replace_malloc.c:220) ==12655== by 0x62041CD: QWaitCondition::QWaitCondition() (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x6200EAF: ??? (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x62010A0: ??? (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x6203132: QThreadData::current() (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x62FC4BC: QObject::QObject(QObject*) (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x4008D2: main (in /tmp/Qt/bin/leak) ==12655== ==12655== 120 bytes in 1 blocks are still reachable in loss record 4 of 7 ==12655== at 0x4C229C7: operator new(unsigned long) (vg_replace_malloc.c:220) ==12655== by 0x61FE681: QMutex::QMutex(QMutex::RecursionMode) (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x6200DC8: QThreadData::QThreadData(int) (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x620310C: QThreadData::current() (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x62FC4BC: QObject::QObject(QObject*) (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x4008D2: main (in /tmp/Qt/bin/leak) ==12655== ==12655== 120 bytes in 1 blocks are still reachable in loss record 5 of 7 ==12655== at 0x4C229C7: operator new(unsigned long) (vg_replace_malloc.c:220) ==12655== by 0x61FE681: QMutex::QMutex(QMutex::RecursionMode) (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x6200DE9: QThreadData::QThreadData(int) (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x620310C: QThreadData::current() (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x62FC4BC: QObject::QObject(QObject*) (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x4008D2: main (in /tmp/Qt/bin/leak) ==12655== ==12655== 120 bytes in 1 blocks are still reachable in loss record 6 of 7 ==12655== at 0x4C229C7: operator new(unsigned long) (vg_replace_malloc.c:220) ==12655== by 0x61FE681: QMutex::QMutex(QMutex::RecursionMode) (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x6200E77: ??? (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x62010A0: ??? (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x6203132: QThreadData::current() (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x62FC4BC: QObject::QObject(QObject*) (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x4008D2: main (in /tmp/Qt/bin/leak) ==12655== ==12655== 176 bytes in 1 blocks are still reachable in loss record 7 of 7 ==12655== at 0x4C229C7: operator new(unsigned long) (vg_replace_malloc.c:220) ==12655== by 0x6201092: ??? (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x6203132: QThreadData::current() (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x62FC4BC: QObject::QObject(QObject*) (in /usr/lib/libQtCore.so.4.5.2) ==12655== by 0x4008D2: main (in /tmp/Qt/bin/leak) ==12655== ==12655== LEAK SUMMARY: ==12655== definitely lost: 0 bytes in 0 blocks ==12655== indirectly lost: 0 bytes in 0 blocks ==12655== possibly lost: 0 bytes in 0 blocks ==12655== still reachable: 744 bytes in 7 blocks ==12655== suppressed: 0 bytes in 0 blocks ==12655== ==12655== For counts of detected and suppressed errors, rerun with: -v ==12655== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 8 from 8) </pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USmalat
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs anyone using valgrind and Qt?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIs anyone using valgrind and Qt?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POIs anyone using valgrind and Qt?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload