Databases
StackOverflow2013
Postsdbo
POMemory leak checking on Windows with QT and MinGW32
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMemory leak checking on Windows with QT and MinGW32
    text
    copied!<p>Lately I have been developing in C++ with QT Creator. All is well and I'm nearly at the point of packaging and distributing my application. But obviously before any release you better make sure you have everything right. So I'm at the testing stage, and something tells me that I have some slight memory issues. Nothing serious, but I like to obsess over these ;-).</p> <p>So I decided to try some memory leak detection libraries. For starters I looked at <a href="https://stackoverflow.com/questions/413477/is-there-a-good-valgrind-substitute-for-windows">this</a> question. I disregarded Purify and Insure++ because of the costs. Someone else suggested to use the MSVC compiler so I could use the CRT memory validation routines. Which I considered but decided against for now because of the implications it would have on using the debugger from within QT Creator.</p> <p>Then I stumbled across <a href="http://duma.sourceforge.net/README.txt" rel="nofollow noreferrer">DUMA</a> which I got to compile using the MinGW32 compiler that comes with QT. However, I found that it doesn't really play well with QT because of the incredible amount of segmentation faults. I know they are how DUMA works, but I'm pretty sure I did not screw things up as much as DUMA tried to make me believe.</p> <p>Another something I tried was the <a href="http://code.google.com/p/google-perftools/" rel="nofollow noreferrer">google-performance-tools</a> which I sadly cannot get to compile with the MinGW32 version supplied with QT, even if I add in the required dependencies.</p> <p>All of this brings me to my question: Is there any working solution out there for QT Creator developers that want to check their programs for memory leaks?</p> <p>Thanks,</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload