Summary: | Crash after start of kde | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Eric Thiele <bugs> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Eric Thiele
2010-05-18 10:35:47 UTC
Crashes caused by memory corruption are hard to debug unless you can provide steps to reproduce the bug or a valgrind log. As Christoph said, if its reproduceable we need a valgrind log, if not we can't really do anything about it. the bug was produced by defect Memory module, I'm verry sorry for the noise. But kdevelop was the only misbahving programm on server. Best regards, Eric Thiele |