3 ms·
The QT C++ framework consciously decides to not deallocate the stuff that only get allocated once. The result is that running leaking catching tools is very har
by joe_the_user 13y ago
The QT C++ framework consciously decides to not deallocate the stuff that only get allocated once. The result is that running leaking catching tools is very hard. Not necessarily the greatest outcome despite being a logically defensible move.
- lmm 13y agoQT is big and popular enough that I would expect tools to have support for it.
- gngeal 13y agoWouldn't a creation of the equivalent of a permspace and instructing said tools to ignore it mitigate the problem?
- joe_the_user 13y agoIt might but that would be a matter for whoever is now developing QT itself.
- icefox 13y agoCan you be more specific? The common case in Qt (not QT) is that a QObject has a parent and when the parent is destroyed all of the children are too.
- joe_the_user 13y agoSee: http://stackoverflow.com/questions/1593717/is-anyone-using-valgrind-and-qt http://stackoverflow.com/questions/1593717/is-anyone-using-v... When I googled that, I found QT apparent has created some suppression files to help with using Valgrind. But I'm pretty sure that's recent and users struggled for a while with QT's approach. http://developer.nokia.com/Community/Wiki/Using_valgrind_with_Qt_Creator http://developer.nokia.com/Community/Wiki/Using_valgrind_wit...