[frameworks-kcrash] [Bug 409961] Dr.Konqui doesn't report plasmashell crash when using Wayland
https://bugs.kde.org/show_bug.cgi?id=409961 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #9 from Nicolas Fella --- If plasmashell (or something else) crashes because of a Wayland protcol error (which is somewhat common, see https://bugs.kde.org/show_bug.cgi?id=447717) then there will be no coredump/DrKonqi does't trigger -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcrash] [Bug 409961] Dr.Konqui doesn't report plasmashell crash when using Wayland
https://bugs.kde.org/show_bug.cgi?id=409961 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcrash] [Bug 409961] Dr.Konqui doesn't report plasmashell crash when using Wayland
https://bugs.kde.org/show_bug.cgi?id=409961 --- Comment #8 from Patrick Silva --- I just noticed that this issue also affects X11 session. Drkonqi shows the same "The debugger has quit unexpectedly" message seen in my screenshot. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcrash] [Bug 409961] Dr.Konqui doesn't report plasmashell crash when using Wayland
https://bugs.kde.org/show_bug.cgi?id=409961 Harald Sitter changed: What|Removed |Added Assignee|unassigned-b...@kde.org |fa...@kde.org Status|NEEDSINFO |REPORTED CC||kdelibs-b...@kde.org Resolution|WAITINGFORINFO |--- Product|drkonqi |frameworks-kcrash Version|unspecified |5.60.0 Component|general |general --- Comment #7 from Harald Sitter --- Right, so I *think* I've found it happening, but it's not really drkonqi's fault. What likely happens is that GIO is being used by something (in my case discover) and GIO will trip over a filedescriptor that was closed by KCrash before drkonqi starts. GIO has a forced fatality attached to this so essentially plasmashell crashes while we are trying to trace the crash. I've not really found an easy way to prevent this. Possibly coordinate closing with drkonqi may prevent this sort of problem. I.e. since we now have a socket from kcrash to drkonqi we could have drkonqi tell kcrash when it SIGSTOP'ed the process, at this point kcrash can safely close the file descriptors without risking that a still running thread will fall over the closed FD. Alas, I don't really know enough about this, or even if there is a reason that the FDs are closed before starting drkonqi. -- You are receiving this mail because: You are watching all bug changes.
