[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#974602: libqt5core5a: Upstream issue with QProcess breaks debugging with QtCreator in 5.15.1



Package: libqt5core5a
Version: 5.15.1+dfsg-2
Severity: important
Tags: upstream patch

We (as QGIS developers) hit this today:
https://lists.osgeo.org/pipermail/qgis-developer/2020-November/062625.html

Since recent Qt update to 5.15.1 in Debian, QtCreator fails to debug Qt-Applications
(like QGIS) because of an upstream issue related to gdb, lldb and the use 
of QProcess in applications:
https://bugreports.qt.io/browse/QTBUG-86319

There seems to be an upstream fix:
https://codereview.qt-project.org/c/qt/qtbase/+/313535
of which myself I cannot check if it is OK.
I do not have enough knowledge about how to handle this: wait for 5.15.2? 
Or try to get this patch into debian (like Fedora did apparently, see osgeo thread).

Hope this is enough information. If you need more information let me know.
More experienced Qt/QGIS devs will probably respond on the osgeo/qgis dev list.

Regards,
Richard Duivenvoorde


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libqt5core5a depends on:
ii  libc6                  2.31-4
ii  libdouble-conversion3  3.1.5-6
ii  libgcc-s1              10.2.0-16
ii  libglib2.0-0           2.66.2-1
ii  libicu67               67.1-4
ii  libpcre2-16-0          10.34-7
ii  libstdc++6             10.2.0-16
ii  libzstd1               1.4.5+dfsg-4
ii  shared-mime-info       2.0-1
ii  zlib1g                 1:1.2.11.dfsg-2

Versions of packages libqt5core5a recommends:
ii  qttranslations5-l10n  5.15.1-2

Versions of packages libqt5core5a suggests:
ii  libthai0  0.1.28-3

-- no debconf information


Reply to: