StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><a href="http://www.efnetcpp.org/wiki/Heap_Corruption" rel="nofollow">http://www.efnetcpp.org/wiki/Heap_Corruption</a></p> <p>Are you freeing/deleting something twice or referring to a variable that has been deleted?</p> <p>The last time I had errors all over the map in a fairly random fashion it was because of Heap Corruption.</p> <p>Qt often uses a kind of Smart Pointer to keep track of what needs to be deleted and what doesn't. (Keeping track of how many references are opened and stored and when those references get deleted.) I would look at any variables that get shared by multiple objects.</p> <p>Here are some other Qt resources for debugging:</p> <p><a href="http://qt-project.org/doc/qt-4.8/debug.html" rel="nofollow">http://qt-project.org/doc/qt-4.8/debug.html</a></p> <p><a href="http://qt-project.org/doc/qt-4.8/qobject.html#dumpObjectInfo" rel="nofollow">http://qt-project.org/doc/qt-4.8/qobject.html#dumpObjectInfo</a></p> <p><a href="http://qt-project.org/doc/qt-4.8/qobject.html#dumpObjectTree" rel="nofollow">http://qt-project.org/doc/qt-4.8/qobject.html#dumpObjectTree</a></p> <p>Understanding and using the Qt Object model correctly, and correctly parenting objects can also be helpful in tracking down weird bugs.</p> <p><a href="http://qt-project.org/doc/qt-4.8/object.html" rel="nofollow">http://qt-project.org/doc/qt-4.8/object.html</a></p> <p>Another way of narrowing down the bug, is by block commenting out sections of code until the bug disappears, and then work backwards, adding code back in.</p> <p>And finally another way to find a bug like this, is to make use of the versioning tool that you have been using on a regular basis (right?). Revert back to a version that didn't have the bug, then do a diff with the current version and start with those differences first.</p> <p>Hope that helps.</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