[Qt-interest] QTimer and crashing...

[Colin S. Miller]

Brad Howes wrote:
 > On Aug 3, 2010, at 9:36 PM, william.crocker at analog.com wrote:
 >
 >> Can you say, "valgrind"?
 >
 >
 > Why?
 >

Quoth the OP
    On one instance (and only one instance out of dozens of
    crashes) GDB reported a memory corruption error.
Endth quote.


Since there is memory corruption and the OP appears to be
using a POSIX-compatible OS, then valgrind is the
obvious choice.

Valgrind will report invalid memory access before it can cause
the program to crash. The latest versions will report when
initialised data is accessed at all, older version only
tracked uninitialised data and reported when the data was used
for flow-control or I/O.

HTH,
Colin S. Miller


-- 
Replace the obvious in my email address with the first three letters of the hostname to reply.