Summary: | crash after start (glibc: double free or corruption) | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Nikita Melnichenko <open-development> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | 4.0.1 | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | valgrind log |
Description
Nikita Melnichenko
2010-05-24 09:44:28 UTC
Created attachment 43834 [details]
valgrind log
This is not the first time when this bug appears for me. What can help if you stuck in this crash cycle: 1. Move .kdev4 file from it's place. 2. Load kdevelop, it will complain about missing project. 3. Start a new session, close the one with your project, then close this new session. 4. Move project file back. 5. Load kdevelop, switch to your session. The valgrind log is unfortunately useless, it doesn't contain any information about where the corruption occurs. Did you run kdevelop via KDEV_SESSION=blah valgrind --trace-origins=yes kdevelop.bin? *** This bug has been marked as a duplicate of bug 236434 *** |