summaryrefslogtreecommitdiffstats
path: root/doc/src/snippets/code/src_sql_kernel_qsqlerror.cpp
diff options
context:
space:
mode:
authorKent Hansen <kent.hansen@nokia.com>2011-01-28 09:10:31 (GMT)
committerKent Hansen <kent.hansen@nokia.com>2011-01-28 09:53:49 (GMT)
commitb127b1036ec75c625920a6c029b64a95e3702bf9 (patch)
tree6293c86030cdcd45e5cbb2a0ef5d9c3fab3b6f0b /doc/src/snippets/code/src_sql_kernel_qsqlerror.cpp
parentead20f4c1edc2e1c5c39f47bf7c9e56600d6362b (diff)
downloadQt-b127b1036ec75c625920a6c029b64a95e3702bf9.zip
Qt-b127b1036ec75c625920a6c029b64a95e3702bf9.tar.gz
Qt-b127b1036ec75c625920a6c029b64a95e3702bf9.tar.bz2
Invalidate QScriptPrograms when engine is destroyed
If the engine is destroyed before the program, the program must be invalidated; otherwise the program destructor will access a stale engine pointer, which can cause a crash (it crashes on Symbian, but "only" gives a Valgrind warning on Linux for our autotests). We need to keep track of all associated programs, just like we already do for values and strings. This fix follows the exact same pattern, but uses a QSet to keep the patch minimal. No new tests, but the evaluateProgram() test runs successfully on Symbian now, and there are no more Valgrind warnings. Task-number: QTBUG-16987 Reviewed-by: Olivier Goffart
Diffstat (limited to 'doc/src/snippets/code/src_sql_kernel_qsqlerror.cpp')
0 files changed, 0 insertions, 0 deletions