https://bugs.kde.org/show_bug.cgi?id=410636
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #3 from Harald Sitter <sit...@kde.org> ---
It's one of the most illusive crashes I've seen.
It affects fairly unrelated apps, doesn't always have the same call chain, but
most of all I don't actually see how the code could crash there. Also, all
other reports have zero worthwhile information beyond the backtrace.
So, what I would like you to do is:
- install systemd-coredump
- make sure it is set up correctly (/proc/sys/kernel/core_pattern should be set
to invoke it)
- maybe test by using kill -SEGV on a terminal process
- disable kcrash by adding KDE_DEBUG=1 to your /etc/environment
- restart and trigger the bug
coredumpctl will then able to catch a super accurate core and context of the
crash. Please post the coredumpctl info of the crash and check if there might
be other crashes that happen around the same time.
Additionally please check your .xession-errors, journald/syslog for relevant
information around the time the crash occurs (coredumpctl will be able to give
you the accurate time it crashed).
It's a long shot but the crash may be a symptom of something else. The code in
question to do with QStringList, while involving pointers, should not really be
able to crash, certainly not while the qapplication loop is still running. So,
I wouldn't even begin to figure out what is wrong without patching Qt and
seeing what happens.
>From related bugs I could find it looks like this crash appears seemingly
randomly and then disappears again and has no discernible pattern beyond the
top most stack frame being the QStringList contains.
--
You are receiving this mail because:
You are watching all bug changes.
