Re: Memory leak in QSettings

[Dimitri]

Hi,

> I know about these tools. The funny thing is that I were just happy 
> using this easy and cheap compiled-in "macro-way" to discover memleaks 
> up to the point we started using Qt in our project. And now we will have 
> to consider another way. ;-/

It's hard to make good memory debuggers. One common issue with "easy and 
cheap" tools : memory may be released after main() has returned (in 
static object destructors for example) and this may be flagged as a 
memory leak. I think many macro-based "easy and cheap" tools do not 
handle this. Even the tool bundled with Visual Studio used not to (or 
does not) handle this.

--
Dimitri

--
To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with 
"unsubscribe" in the subject or the body.
List archive and information: http://lists.trolltech.com/qt-interest/