Summary: | KDevelop crashes upon opening a session. | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Łukasz Kucharski <luk32> |
Component: | Build tools: CMake | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | aleixpol, andrew.crouthamel |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | 4.2.60 | ||
Target Milestone: | 4.2.3 | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Łukasz Kucharski
2011-09-27 06:08:02 UTC
Can you remember what project was it? Can you reproduce? Backtraces ending in stuff like QList::append etc. usually point to either a binary compatibility, a memory corruption or a null-pointer on the object that has the list as member. The latter is probably not the reason here since the code accesses other members first. So a valgrind log and reproduction recipe are necessary here. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! I think it's fair to close. I don't think I even have the project around. This report was sent from the crash tool as far as I can recall. Sorry for not providing the needed info. No problem, thank you for the update! |