Reply to dieser Memory Leak mein Problem? on Sat, 08 Jul 2006 13:27:41 GMT

gggoi — Sat, 08 Jul 2006 13:27:41 GMT

Hallo ich bekomme folgenden Memory Leak in meiner Anwendung die in QT/C++ geschrieben ist. Laut QT werden Heap-Objekte selbst gelöscht sobald das parent destroyed wird...ich habe also nirgends ein delete aufgerufen...

==6668== Invalid read of size 4
==6668==    at 0x1C546184: (within /lib/tls/libc-2.3.2.so)
==6668==    by 0x1C54658C: (within /lib/tls/libc-2.3.2.so)
==6668==    by 0x1C5C1FF6: (within /lib/tls/libc-2.3.2.so)
==6668==    by 0x1C63C422: (within /lib/tls/libc-2.3.2.so)
==6668==    by 0x1C63C337: (within /lib/tls/libc-2.3.2.so)
==6668==    by 0x1C63C6C4: __libc_freeres (in /lib/tls/libc-2.3.2.so)
==6668==    by 0x1B8FEA08: _vgw(float, long double,...)(...)(long double,...)(short) (vg_intercept.c:55)
==6668==    by 0x1C55A1C5: exit (in /lib/tls/libc-2.3.2.so)
==6668==    by 0x1C54497D: __libc_start_main (in /lib/tls/libc-2.3.2.so)
==6668==    by 0x804FAB0: ??? (start.S:102)
==6668==  Address 0x1C926080 is 32 bytes inside a block of size 60 free'd
==6668==    at 0x1B906B04: free (vg_replace_malloc.c:152)
==6668==    by 0x1C546D37: (within /lib/tls/libc-2.3.2.so)
==6668==    by 0x1C605902: (within /lib/tls/libc-2.3.2.so)
==6668==    by 0x1C6057A6: tdestroy (in /lib/tls/libc-2.3.2.so)
==6668==    by 0x1C63C1C1: (within /lib/tls/libc-2.3.2.so)
==6668==    by 0x1C63C6C4: __libc_freeres (in /lib/tls/libc-2.3.2.so)
==6668==    by 0x1B8FEA08: _vgw(float, long double,...)(...)(long double,...)(short) (vg_intercept.c:55)
==6668==    by 0x1C55A1C5: exit (in /lib/tls/libc-2.3.2.so)
==6668==    by 0x1C54497D: __libc_start_main (in /lib/tls/libc-2.3.2.so)
==6668==    by 0x804FAB0: ??? (start.S:102)

ich kann hier nirgendwo ein file von mir finden. Ist dieser memory leak trotzdem mein Problem?