also, you may want to look into possibly updating you libraries because I get very different output from valgrind with full memory leak checking.
Code:
==26507== IN SUMMARY: 36 errors from 3 contexts (suppressed: 7 from 1)
==26507==
==26507== malloc/free: in use at exit: 308,231 bytes in 3,824 blocks.
==26507== malloc/free: 164,138 allocs, 160,314 frees, 10,879,333 bytes allocated.
==26507==
==26507== searching for pointers to 3,824 not-freed blocks.
==26507== checked 907,240 bytes.
==26507==
==26507==
==26507== 20 bytes in 1 blocks are definitely lost in loss record 30 of 116
==26507== at 0x40245D8: malloc (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==26507== by 0x4ACDF8A: strdup (in /lib/libc-2.4.so)
==26507==
==26507==
==26507== 156 (36 direct, 120 indirect) bytes in 1 blocks are definitely lost in loss record 71 of 116
==26507== at 0x40245D8: malloc (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==26507== by 0x4B43F54: (within /lib/libc-2.4.so)
==26507==
==26507==
==26507== 216 bytes in 1 blocks are definitely lost in loss record 77 of 116
==26507== at 0x40245D8: malloc (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==26507== by 0x46D5379: _XimOpenIM (in /usr/lib/libX11.so.6.2.0)
==26507==
==26507==
==26507== 2,038 bytes in 2 blocks are definitely lost in loss record 101 of 116
==26507== at 0x40245D8: malloc (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==26507== by 0x45C7BBA: (within /usr/lib/libfreetype.so.6.3.8)
==26507==
==26507== LEAK SUMMARY:
==26507== definitely lost: 2,310 bytes in 5 blocks.
==26507== indirectly lost: 120 bytes in 10 blocks.
==26507== possibly lost: 0 bytes in 0 blocks.
==26507== still reachable: 305,801 bytes in 3,809 blocks.
==26507== suppressed: 0 bytes in 0 blocks.
it doesn't seem from this output with my version of things, there are no leaks which can be traced back to a QT/Debugger object.
QT version 4.1.4, glibc version 2.4, gcc version 4.1.1
proxy
Bookmarks