From 60176efa7843fda048b2eb5d347fab0dd991e26d Mon Sep 17 00:00:00 2001 From: Simon Hausmann Date: Wed, 23 May 2018 12:55:11 +0200 Subject: Fix crash when incubating objects with non-existent initial properties When incubation is triggered from C++ and reaches the state of setting the initial properties (as supplied to incubateObject), we'd set engine->currentStackFrame to a CppStackFrame that provides access to the correct QML context. As we're not called from the interpreter, the v4Function pointer would be a null pointer. If during the initial property setting an exception is thrown (due to non-existent property access) and a back-trace is created, we'd end up dereferencing v4Function. Change-Id: I7f6b0ba7893bfb4186f55d4c213b4bb602d29aa0 Task-number: QTBUG-68416 Reviewed-by: Lars Knoll --- tests/auto/qml/qqmlcomponent/data/InitialPropertyTest.qml | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 tests/auto/qml/qqmlcomponent/data/InitialPropertyTest.qml (limited to 'tests/auto/qml/qqmlcomponent/data/InitialPropertyTest.qml') diff --git a/tests/auto/qml/qqmlcomponent/data/InitialPropertyTest.qml b/tests/auto/qml/qqmlcomponent/data/InitialPropertyTest.qml new file mode 100644 index 0000000000..7de276f2d8 --- /dev/null +++ b/tests/auto/qml/qqmlcomponent/data/InitialPropertyTest.qml @@ -0,0 +1,4 @@ +import QtQml 2.0 +QtObject { + property bool ok: false +} -- cgit v1.2.3