Summary: | build of jan 13 crashing in kstartupinfoid | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kwindowsystem | Reporter: | Harald Sitter <sitter> |
Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | mgraesslin |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Harald Sitter
2014-01-13 10:18:13 UTC
The backtrace is missing debug information for the relevant part. Please provide a backtrace with file and line numbers. Can't reproduce it anymore -.- More interestingly I have no clue why dbg symbols were broken to begin with... will have a look. (In reply to comment #2) > Can't reproduce it anymore -.- There was such an issue which I fixed months ago (with a very similar backtrace). Maybe something old got picked? Nope that was definitely the expected daily build running on a newly created user. If it pops back up I'll get a new backtrace. The debug symbols will be fixed in tomorrow's build. There may have been display plug'n'play involved though. I'll try to recreate it tomorrow with debug symbols available. Perhaps the crash is dependent on the time of day :S At any rate I wasn't doing anything particularly out of the ordinary so I expect it to pop up again. The crash I fixed was depending on timeouts of kstartup infos. If two timeouts happened in the same minute one got a crash. Extremely random, so time of date might matter ;-) |