Hello,
I don't know if I'm the only one person in this case but tracker-indexer
"loses" some files proposed by trackerd for indexing.
In trackerd.log, I see :
27 aoû 2008, 23:05:59: Tracker: Indexed 1976/89459, module:'files', 02h
18m left, 03m 07s elapsed
and then nothing!
and tracker-indexer a
On Wed, 2008-08-27 at 23:20 +0200, Laurent Aguerreche wrote:
> I don't know if I'm the only one person in this case but tracker-indexer
> "loses" some files proposed by trackerd for indexing.
>
> In trackerd.log, I see :
> 27 aoû 2008, 23:05:59: Tracker: Indexed 1976/89459, module:'files', 02h
>
Selon Philip Van Hoof <[EMAIL PROTECTED]>:
> On Wed, 2008-08-27 at 23:20 +0200, Laurent Aguerreche wrote:
>
> > I don't know if I'm the only one person in this case but tracker-indexer
> > "loses" some files proposed by trackerd for indexing.
> >
> > In trackerd.log, I see :
> > 27 aoû 2008, 23:0
On Thu, 2008-08-28 at 12:31 +0200, [EMAIL PROTECTED] wrote:
> You're right, tracker-indexer crashes.
>
>
> (gdb) bt
> #0 0x00418701 in tracker_indexer_module_file_iter_contents (
> module=0x29e3900, file=0x0) at tracker-indexer-module.c:213
> #1 0x004155e4 in process_file (
Laurent, would it be possible for you to run the indexer under valgrind?
Valgrind might reveal some interesting things, perhaps
On Thu, 2008-08-28 at 13:06 +0200, Philip Van Hoof wrote:
> On Thu, 2008-08-28 at 12:31 +0200, [EMAIL PROTECTED] wrote:
>
> > You're right, tracker-indexer crashes.
>
Hi Laurent!,
On jue, 2008-08-28 at 12:31 +0200, [EMAIL PROTECTED] wrote:
> Selon Philip Van Hoof <[EMAIL PROTECTED]>:
>
> > On Wed, 2008-08-27 at 23:20 +0200, Laurent Aguerreche wrote:
> >
> > > I don't know if I'm the only one person in this case but tracker-indexer
> > > "loses" some files prop
Le jeudi 28 août 2008 à 14:03 +0200, Carlos Garnacho a écrit :
> Hi Laurent!,
Hi,
> On jue, 2008-08-28 at 12:31 +0200, [EMAIL PROTECTED] wrote:
> > Selon Philip Van Hoof <[EMAIL PROTECTED]>:
> >
> > > On Wed, 2008-08-27 at 23:20 +0200, Laurent Aguerreche wrote:
> > >
> > > > I don't know if I'm
On Thu, 2008-08-28 at 20:28 +0200, Laurent Aguerreche wrote:
> Le jeudi 28 août 2008 à 14:03 +0200, Carlos Garnacho a écrit :
> > Hi Laurent!,
>
> Hi,
>
> > On jue, 2008-08-28 at 12:31 +0200, [EMAIL PROTECTED] wrote:
> > > Selon Philip Van Hoof <[EMAIL PROTECTED]>:
> > >
> > > > On Wed, 2008-08-
Hi Laurent :),
Just committed the fix for a bug that could be causing your issues,
would you mind to update and test? :)
Thanks!
Carlos
On jue, 2008-08-28 at 12:31 +0200, [EMAIL PROTECTED] wrote:
> Selon Philip Van Hoof <[EMAIL PROTECTED]>:
>
> > On Wed, 2008-08-27 at 23:20 +0200, Laurent Agu
Le vendredi 29 août 2008 à 15:49 +0200, Carlos Garnacho a écrit :
> Hi Laurent :),
Hi!
> Just committed the fix for a bug that could be causing your issues,
> would you mind to update and test? :)
In some ways it fixes my issues since tracker-indexer doesn't index
anything anymore! :-)
tracker
did you reindex?
jamie
On Sun, 2008-08-31 at 19:42 +0200, Laurent Aguerreche wrote:
> Le vendredi 29 août 2008 à 15:49 +0200, Carlos Garnacho a écrit :
> > Hi Laurent :),
>
> Hi!
>
> > Just committed the fix for a bug that could be causing your issues,
> > would you mind to update and test? :)
> This is quite strange, Philip and me have been thinking a while and
> can't identify what could cause this. There are a few open questions:
>
> - Was it scanning a summary/mbox?
> - In that case, was is just opened for indexing, or did it happen in the
> middle of the processing
> - Does valgri
Le dimanche 31 août 2008 à 15:35 -0400, Jamie McCracken a écrit :
> did you reindex?
Yes, and I also removed files in ~/.local, ~/.cache and /tmp
Laurent.
> jamie
>
>
> On Sun, 2008-08-31 at 19:42 +0200, Laurent Aguerreche wrote:
> > Le vendredi 29 août 2008 à 15:49 +0200, Carlos Garnacho a é
Jamie McCracken wrote:
>>> that should also save every debug message to
>>> ~/.local/share/tracker/tracker-indexer.log, it'd also be useful to see
>>> the last messages before the crash.
>> A question: how do you compile all the code with -g for debugging?
>> In the past, "configure" had --enable-d
Jamie McCracken wrote:
> Another potential crasher - unlike trunk get_file_content does no utf-8
> validation and also if file is bigger than MAX_TEXT cuts it off which is
> likely to not land on a valid utf-8 word break
This is true.
> ideally do what trunk does and read file line by line so tha
On Tue, 2008-09-02 at 12:14 +0100, Martyn Russell wrote:
> Jamie McCracken wrote:
> > Another potential crasher - unlike trunk get_file_content does no utf-8
> > validation and also if file is bigger than MAX_TEXT cuts it off which is
> > likely to not land on a valid utf-8 word break
>
> This is
Jamie McCracken wrote:
> On Tue, 2008-09-02 at 12:14 +0100, Martyn Russell wrote:
>> Jamie McCracken wrote:
>>> Another potential crasher - unlike trunk get_file_content does no utf-8
>>> validation and also if file is bigger than MAX_TEXT cuts it off which is
>>> likely to not land on a valid utf-
17 matches
Mail list logo
