[SDK] Sailfish OS SDK crashes

asked 2018-08-09 00:19:13 +0200

Alex gravatar image

I am experiencing the issue that the Sailfish OS SDK is crashing on a regular basis (almost daily). This issue persists with different SDK versions and I am experiencing this at least since December 2017.

The latest crash occured with the SDK version 1804 (SFOS 2.2.0.29). Everytime the SDK crashed with the following error:

qtcreator: Fatal IO error 10 (no child processes) on X server :0.

I am using the SDK on a system running Ubuntu 16.04 LTS (64 bit).

There is no recognisable correlation and the SDK crashes in all cases: while being used and while being idle and also with and without running build engine/emulator.

edit retag flag offensive close delete

Comments

@Alex Would you be able to provide a backtrace?

martyone ( 2018-08-09 06:46:37 +0200 )edit

@martyone Sure, I just need to know how to do that. :)

Alex ( 2018-08-09 07:11:48 +0200 )edit
1

@Alex The easiest option could be to run Qt Creator under GDB (gdb ~/SailfishOS/bin/qtreator, then run inside GDB session) and print the backtrace using backtrace command inside GDB session when Qt Creator crashes.

martyone ( 2018-08-09 08:39:41 +0200 )edit

@martyone Well using gdp does not work as expected: If qtcreator crashes inside the gdb session then gdb won't return to the gdb prompt and the gdb process will stall at 100% CPU usage. I am unable to kill the process and have to reboot my system (or use kill -9 GDBpid)... The gdb session during the qtcreator crash looks something like this everytime:

[...]
[New Thread 0x7fff33fff700 (LWP 6366)]
[Thread 0x7fff33fff700 (LWP 6366) exited]
[Thread 0x7fff4e7fc700 (LWP 6365) exited]
qtcreator: Fatal IO error 10 (no child processes) on X server :0.
[Thread 0x7fffe232b700 (LWP 3789) exited]
[...]

Also the qtcreator is missing debug symbols, could you provide an executable with debug symbols?

Alex ( 2018-08-14 12:46:06 +0200 )edit
1

@Alex It might help running Qt Creator standalone and attach GDB to it later with gdb -p <pid>.

Also try to collect the debug output by running Qt Creator this way: QT_LOGGING_RULES='*=true' ~/SailfishOS/bin/qtcreator |& tee qtc.log.

Providing debug symbols would take some time, let's try without it first.

martyone ( 2018-08-14 18:32:52 +0200 )edit