https://bugs.kde.org/show_bug.cgi?id=410636
--- Comment #4 from Jaak Ristioja <j...@ristioja.ee> --- (In reply to Harald Sitter from comment #3) > - install systemd-coredump I'm not using systemd so I don't think this will be an option. However, I think I could still use the gcore command-line utility to generate a core dump (or attach GDB to the crashed process and use the gcore command). > - restart and trigger the bug ...if it triggers. Because I haven't seen it lately. I also tried logging in and out again (+ killall -u username -9) multiple times, but I couldn't reproduce it. > 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. I'll make sure to investigate for any other signs such if it reoccurs. Do you have any references to similar bug reports? Do you think it is a drkonqi issue or rather a Qt issue (e.g. perhaps something similar to QTBUG-39285)? -- You are receiving this mail because: You are watching all bug changes.
