https://bugs.kde.org/show_bug.cgi?id=427246
--- Comment #1 from Igor Kushnir <igor...@gmail.com> ---
FAILED WORKAROUND
Add the following two lines to /etc/security/limits.conf and reboot:
* hard nofile 100000 # necessary for KDevelop
* soft nofile 100000 # necessary for KDevelop
This workaround does not change anything.
INADEQUATE WORKAROUND
Narrowed down the plugins that must be disabled in
~/.local/share/kdevelop/sessions/{<session-id>}/sessionrc to enable launching,
hitting breakpoints in the KDevelop source code and exiting KDevelop without
crashes: KDevCMakeDocumentation, kdevfilemanager, kdevqthelp (I have
kdevperforce and katectagsplugin disabled too, but not sure if that's
necessary). In addition, I had to force-disable kdevclangsupport plugin via
`export KDEV_DISABLE_PLUGINS=kdevclangsupport`. Even without these essential
plugins, opening a project triggers the signals and crashes.
FIX
This is a known Qt 5.15.1 bug: QTBUG-86319 (I found a duplicate of this bug by
searching for "SIGTRAP" on the Qt bug tracker). The corresponding Arch Linux
bug: https://bugs.archlinux.org/task/68001. I applied the fix for the Qt bug
from https://codereview.qt-project.org/c/qt/qtbase/+/314049 and the signals and
crashes are gone!
The fix will be included in Qt 5.15.2. In the meantime, it would be useful if
the qt5-base Arch Linux package included the patch to spare developers from
manually applying the fix after each qt5-base pkgrel update. @{Arch Linux users
affected by this bug}, please create an issue on the Arch bug tracker or reopen
FS#68001 (closed because this turned out to be not a GDB issue) and request the
qt5-base patch.
--
You are receiving this mail because:
You are watching all bug changes.
