/proc/$PID/exe is a link to the executable. You can load that executable
into gdb and attach to the hung process. Then you will probably discover
that important debug symbols are missing but it's a different matter.
As an example, let's say process 1117 has hung:
[root@Sailfish ~]# ls -la /pro
No, I didn't. Its QML/Python app, so it is not clear what I should attach
the debugger to. sailfish-qml?
Rinigus
On Sun, Sep 9, 2018 at 12:35 PM Slava Monich wrote:
> Have you tried debugging with a debugger (run the app under gdb and
> examine the backtrace when it gets stuck)? That seems to b
Have you tried debugging with a debugger (run the app under gdb and
examine the backtrace when it gets stuck)? That seems to be the obvious
first step to me.
Cheers,
-Slava
We debugged a failure to initiate destruction further. As suggested
by @wdehoog, I added
Connections {
ta
We debugged a failure to initiate destruction further. As suggested
by @wdehoog, I added
Connections {
target: __quickWindow
onClosing: console.log("")
}
to ApplicationWindow. This one does get called during app closure, without
further propagation over to destruction
