Summary: | Crash when building cmake project | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | pclausen <petermichaelclausen> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | NOR | ||
Version: | 4.3.60 | ||
Target Milestone: | 4.3.0 | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | valgrind output |
Description
pclausen
2012-04-23 16:24:11 UTC
Created attachment 70649 [details]
valgrind output
I dont know excactly how to produce a good valgrind report. I've start kdevelop by:
$ valgrind kdevelop 2> val.err
and reproduced the crash, but the output from valgrind does not make sense to me...
If I can do other stuff to help finding the cause of this issue, please say how.
duplicate, can you reliably reproduce this issue? if so, please tell me how the valgrind report is indeed useless here. what you could try though: run kdebugdialog, enable all kdev* debug areas, run kdevelop from a cli and pipe all debug output into some file, reproduce the crash, and then attach the info to bug 266283 thanks *** This bug has been marked as a duplicate of bug 266283 *** |