On segunda-feira, 8 de julho de 2013 10.55.02, Jonathan Greig wrote: > Can you please explain your reasoning or how it might go wrong as "barely > more" sounds exactly what I want and what Alex is asking for. My reasoning > is that it catches all of MY memory leaks, but supresses the gazillions of > memory leaks that aren't directly created by me (Such as memory leaks > within Qt or one of it's dependencies).
It also suppresses memory leaks you caused but happened to include Qt in the calls stack, such as when your slots or event handlers are called from the event loop or when memory is allocated by Qt on your behalf. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
