Hi,
for 'ages' I have been using a standard procedure to debug apps on Suse, developed using MPI and e.g. Python. However on Leap 15.1 this standard procedure crashes with many QT warnings and errors, which are beyond me. The procedure for the parallel debugging session simply is to invoke a small number of processes on the command line like so
where each process runs its own debugger (for Python, ipdb) within a terminal (eg. xterm).
Now, on Leap 15.1, interacting with the debugger within each of the xterms forked will eventually produce stuff like
a/o
Primarily this happens, if one tries to step or run between breakpoints.
Just to be absolutely clear, the app "myapp.py" is free of QT-code or graphics. I.e. the QT warnings/errors stem from the operating system.
Any help to fix this would be most appreciated.
wbwb
for 'ages' I have been using a standard procedure to debug apps on Suse, developed using MPI and e.g. Python. However on Leap 15.1 this standard procedure crashes with many QT warnings and errors, which are beyond me. The procedure for the parallel debugging session simply is to invoke a small number of processes on the command line like so
Code:
mpiexec -n 2 xterm -geometry 80x20 -e ipdb myapp.pyNow, on Leap 15.1, interacting with the debugger within each of the xterms forked will eventually produce stuff like
Code:
WARNING: QApplication was not created in the main() thread.Code:
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QApplication(0x7fdd40001e90), parent's thread is QThread(0x7fdd40006390), current thread is QThread(0x7fdd400262f0)Just to be absolutely clear, the app "myapp.py" is free of QT-code or graphics. I.e. the QT warnings/errors stem from the operating system.
Any help to fix this would be most appreciated.
wbwb