[kdevelop] [Bug 427246] SIGTRAP/SIGSEGV while running any version of KDevelop under GDB after a recent system update

2020-10-02 Thread Francis Herne
https://bugs.kde.org/show_bug.cgi?id=427246 --- Comment #4 from Francis Herne --- Arch just backported the relevant fix in qt5-base 5.15.1-3. I've installed this and gdb works again. Thanks Igor for finding the relevant upstream bug. -- You are receiving this mail because: You are watching all

[kdevelop] [Bug 427246] SIGTRAP/SIGSEGV while running any version of KDevelop under GDB after a recent system update

2020-10-02 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=427246 --- Comment #3 from Igor Kushnir --- (In reply to Francis Herne from comment #2) > As I mentioned on the other bug, one workaround is to start KDevelop and > then use `gdb --pid=`. I haven't tried this workaround from the command line, but attaching to

[kdevelop] [Bug 427246] SIGTRAP/SIGSEGV while running any version of KDevelop under GDB after a recent system update

2020-10-02 Thread Francis Herne
https://bugs.kde.org/show_bug.cgi?id=427246 Francis Herne changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED

[kdevelop] [Bug 427246] SIGTRAP/SIGSEGV while running any version of KDevelop under GDB after a recent system update

2020-10-02 Thread Mate Soos
https://bugs.kde.org/show_bug.cgi?id=427246 Mate Soos changed: What|Removed |Added CC||soos.m...@gmail.com -- You are receiving this mail

[kdevelop] [Bug 427246] SIGTRAP/SIGSEGV while running any version of KDevelop under GDB after a recent system update

2020-10-02 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=427246 --- Comment #1 from Igor Kushnir --- FAILED WORKAROUND Add the following two lines to /etc/security/limits.conf and reboot: * hardnofile 10 # necessary for KDevelop * softnofile 10 # necess