Early "Fatal signal 6 (SIGABRT)" on Android. How to debug?

[torpeanders]

I've compiled my Qt Application for Android. I use Qt 5.7.1 with ndk-r10e for SDK android-25, and deploy to a Nexus 6p running 7.1.1. When I debug/run it crashes before main, and I have no idea how to debug it. All I get in my logs is this:

Starting remote process.I art : Late-enabling -Xcheck:jni
W System : ClassLoader referenced unknown path:
W linker : /data/app/org.qtproject.example.gui-1/lib/arm/libQt5Network.so: unsupported flags DT_FLAGS_1=0x81
W linker : /data/app/org.qtproject.example.gui-1/lib/arm/libQt5Qml.so: unsupported flags DT_FLAGS_1=0x81
W linker : /data/app/org.qtproject.example.gui-1/lib/arm/libQt5Gui.so: unsupported flags DT_FLAGS_1=0x81
W linker : /data/app/org.qtproject.example.gui-1/lib/arm/libQt5Quick.so: unsupported flags DT_FLAGS_1=0x81
W linker : /data/app/org.qtproject.example.gui-1/lib/arm/libQt5Sql.so: unsupported flags DT_FLAGS_1=0x81
W linker : /data/app/org.qtproject.example.gui-1/lib/arm/libQt5Positioning.so: unsupported flags DT_FLAGS_1=0x81
W linker : /data/app/org.qtproject.example.gui-1/lib/arm/libQt5QuickParticles.so: unsupported flags DT_FLAGS_1=0x81
W linker : /data/data/org.qtproject.example.gui/qt-reserved-files/plugins/platforms/android/libqtforandroid.so: unsupported flags DT_FLAGS_1=0x81
W linker : /data/data/org.qtproject.example.gui/qt-reserved-files/plugins/platforms/android/libqtforandroid.so: is missing DT_SONAME will use basename as a replacement: "libqtforandroid.so"
I Qt : qt start
W linker : /data/data/org.qtproject.example.gui/qt-reserved-files/plugins/bearer/libqandroidbearer.so: unsupported flags DT_FLAGS_1=0x81
W linker : /data/data/org.qtproject.example.gui/qt-reserved-files/plugins/bearer/libqandroidbearer.so: is missing DT_SONAME will use basename as a replacement: "libqandroidbearer.so"
W linker : /data/data/org.qtproject.example.gui/qt-reserved-files/plugins/position/libqtposition_android.so: unsupported flags DT_FLAGS_1=0x81
W linker : /data/data/org.qtproject.example.gui/qt-reserved-files/plugins/position/libqtposition_android.so: is missing DT_SONAME will use basename as a replacement: "libqtposition_android.so"
I QtPositioning: Positioning start
I art : Do partial code cache collection, code=18KB, data=28KB
I art : After code cache collection, code=18KB, data=28KB
I art : Increasing code cache capacity to 128KB
I art : Do partial code cache collection, code=40KB, data=62KB
I art : After code cache collection, code=40KB, data=62KB
I art : Increasing code cache capacity to 256KB
D : (null):0 ((null)): QML debugging is enabled. Only use this in a safe environment.
F libc : Fatal signal 6 (SIGABRT), code -6 in tid 10627 (ect.example.gui)

[J.Hilk]

Hi @torpeanders ,

I saw this line

QtPositioning: Positioning start

Are the permissions for that granted? Because this seems to me, that they aren't and that you don't handle that case and simply try to load/access the module anyway. That may very well cause the crash.

[jsulm]

@J.Hilk I don't think this would cause a crash. If the app does not have needed rights then positioning will just not work, but there shouldn't be any crashes because of this.

[J.Hilk]

@jsulm I had this issue, when I tried to access the camera without permission.
The normal objects are created normaly but as soon as I tried to open the camera to get frames -> crash.

[SGaist]

@J-Hilk Wasn't that on iOS ?

[J.Hilk]

@SGaist surprisingly no,

I totoaly expected it to, but e.g. simply compiling the QCamera example for ios, works without any further permission requests. However doesn't work with QLocation that way, afaik.

[SGaist]

That might also depend on which version of iOS you are testing on. IIRC, since 10.8 10.3, applications without the correct permissions and custom explanation message will get killed.

[edit: fixed typo SGaist]

[J.Hilk]

@SGaist
just tested that on ios 10.3.2 and Qt 5.9.1 with the QML-Camera example.
After startup I got the ios generic request for camera permission with Ok or Cancle option. Nothing added/modifed on the example.

If you do not give the permissions, the app won't get killed either.

edit
Non of my devices have ios 10.8. Is that out yet?, Am I so far behind oO?

[SGaist]

Sorry, It was a typo, 10.3.3 got released last week.