| Summary: | KDevelop crashes at startup | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | Juan Ramírez Ruiz <kismonline> |
| Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | cfeck |
| Priority: | NOR | Keywords: | triaged |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Juan Ramírez Ruiz
2010-05-06 09:37:00 UTC
crash is somewhere in kdelibs, either in some kio-stuff or in the kfile library. crash is somewhere in kdelibs, either in some kio-stuff or in the kfile library. see bug 236237 comment 2. you may assign back yourself. ;) (In reply to comment #3) > see bug 236237 comment 2. > you may assign back yourself. ;) I'm not going to, its not kdevelop code accessing kconfig here. your logic is still faulty. by far most crashes in libraries are caused by bad application code, so do your deeds and actually analyze the problem before assigning it away from you. otherwise you can just close it right away. (In reply to comment #5) > your logic is still faulty. by far most crashes in libraries are caused by bad > application code, My experience is different. Often enough the reason is that a library developer didn't forsee how its code could've been used or the library is not documented enough to point out that certain uses need to be avoided. > so do your deeds and actually analyze the problem before > assigning it away from you. otherwise you can just close it right away. How should I? Its not crashing for me (or for any of the other developers), so the only useful thing I can do with such a bugreport is forward to someone/someplace that knows the code and could eventually add some theories as to what might go wrong. (In reply to comment #6) > How should I? > first thing would be requesting a valgrind trace from the user (hello juan :). that might even help when the crash itself is not directly reproducible on request. > forward to someone/someplace that knows the code and could eventually add > some theories as to what might go wrong. > yes, you may get lucky with that. given a 100-frame backtrace which goes through roughly 7 frameworks i'm not too optimistic, though ... in any case it makes more sense to cc instead of reassigning in such doubtful cases. The bug could be related to Samba configuration also, but I doubt that the crash is caused by KConfig. The memory corruption could be caused at any earlier time. This crash report is at least 3 years old and there were no further comments or status updates since then. Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources. If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports (To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED) 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! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |