Summary: | Nepomuk service stub crashes randomly after update to KDE 4.7 (signal: aborted) | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | Cyril Brosch <info> |
Component: | general | Assignee: | Sebastian Trueg <sebastian> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | cfeck, kde, me, trueg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Valgrind log of nepomukserver |
Description
Cyril Brosch
2011-07-31 18:16:00 UTC
Is there a web page or blog that explains how users can run "Nepomuk" through valgrind, so that we can someday get rid of the memory corruption bugs? Michael already has some experience with valgrinding Nepomuk, and volunteered to write some step-by-step debugging guide. And this is his requested reminder message, with a reference to some example crash from 4.7.0 ;) For some serious problem I had to switch back to 4.6.5, anyhow before that I tried to debug the problem with Valgrind, but - of course - every time I attached nepomukstrigiservice (which kept crashing) to Valgrind it did not crash. Nevertheless I attach a Valgrind log from nepomukserver that shows some error messages, which, however, may not be related. Created attachment 62542 [details]
Valgrind log of nepomukserver
[Comment from a bug report cleaner] Backtrace looks similar to the one in bug 275768 Dario, we have well over 100 "memory corruption" crashes in Nepomuk, so comparing backtraces doesn't make much sense. Comparing valgrind backtraces would :) *** This bug has been marked as a duplicate of bug 277810 *** |