I got a temporary access (now revoked) to an arm64 box where I could
reproduce the segfault by running qmlplugindump.
Here's the backtrace:
QV4::Object::defineReadonlyProperty (this=this@entry=0x0, name=0x450bf8,
value=...) at jsruntime/qv4object.cpp:184
184 jsruntime/qv4object.cpp: No such file or directory.
(gdb) bt
#0 QV4::Object::defineReadonlyProperty (this=this@entry=0x0, name=0x450bf8,
value=...) at jsruntime/qv4object.cpp:184
#1 0x0000ffffb7a9f774 in QV4::ObjectPrototype::init (this=0x0,
v4=v4@entry=0x4508f0, ctor=0x0) at jsruntime/qv4objectproto.cpp:84
#2 0x0000ffffb7a5a20c in QV4::ExecutionEngine::ExecutionEngine (this=0x4508f0,
factory=<optimized out>)
at jsruntime/qv4engine.cpp:367
#3 0x0000ffffb7b86d94 in QV8Engine::QV8Engine (this=0x4502a0, qq=<optimized
out>) at qml/v8/qv8engine.cpp:144
#4 0x0000ffffb7a25de8 in QJSEngine::QJSEngine (this=0xfffffffff298, dd=...,
parent=<optimized out>) at jsapi/qjsengine.cpp:201
#5 0x0000ffffb7af738c in QQmlEngine::QQmlEngine (this=0xfffffffff298,
parent=0x0) at qml/qqmlengine.cpp:927
#6 0x00000000004067b8 in main (argc=0, argv=<optimized out>) at main.cpp:1041
Where the code in question is
http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/qml/jsruntime/qv4object.cpp?h=5.6.1#n184
I hope that helps somehow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1630906
Title:
QML segfault on arm64 due to builder kernel change
Status in linux package in Ubuntu:
Confirmed
Status in online-accounts-api package in Ubuntu:
New
Status in qmenumodel package in Ubuntu:
New
Status in qtdeclarative-opensource-src package in Ubuntu:
New
Status in ubuntu-push-qml package in Ubuntu:
New
Status in unity8 package in Ubuntu:
New
Status in webbrowser-app package in Ubuntu:
New
Bug description:
Builders were changed from wily to xenial (4.4) kernel for arm64, and
likely due to this the following kind of errors started happening:
https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64
.ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz
They happen when executing QML code.
I've ruled out that reverting to previous qtbase and qtdeclarative
versions don't affect this, so it's not coming from a Qt change. I've
also verified there's no problem eg on our Bq tablet running the same
tests on xenial+overlay. There are currently no found changes at least
in Qt upstream to backport arm64 related fixes.
Cause is unknown. But the same problem is there on vivid, xenial and yakkety
builds:
https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz
https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz
https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz
This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6,
or glibc 2.21, 2.23 or 2.24.
More logs from affected packages:
https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz
https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz
https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
