[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [nepomuk] [Bug 324307] Nepomukindexer segfaults then core dumps ad finitum using 100% CPU
From: Simeon Bird <bladud () gmail ! com>
Date: 2013-09-03 1:24:50
Message-ID: bug-324307-17878-QboNly0wGD () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=324307
--- Comment #13 from Simeon Bird <bladud@gmail.com> ---
n(In reply to comment #12)
> Sorry, but "ps -ef | grep nepomuk" gives not a single clue as to what file
> it is crashing on.
> What did you expect to see hare?
The indexing service (nepomukfileindexer) makes a list of not-yet-indexed files
and then calls "nepomukindexer $file". I want a copy of the $file the
nepomukindexer is crashing on, so I want the command line arguments of
nepomukindexer.
If ps is not working, could you perhaps try replacing /usr/bin/nepomukindexer
with an (executable) script like:
#!/usr/bin/bash
echo $@ >> some-file-you-can-write-to
then some-file-you-can-write-to should contain the file it crashes on.
(but keep the old /usr/bin/nepomukindexer around somewhere)
--
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic