Re: [Tracker] tracker-indexer does not index all files




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, laurent aguerreche free fr wrote:

You're right, tracker-indexer crashes.


(gdb) bt
#0  0x0000000000418701 in tracker_indexer_module_file_iter_contents (
    module=0x29e3900, file=0x0) at tracker-indexer-module.c:213
#1  0x00000000004155e4 in process_file (indexer=0x1173890, info=0x11e3e60)
    at tracker-indexer.c:1709
#2  0x000000000041590b in process_func (data=0x1173890)
    at tracker-indexer.c:1820
#3  0x0000003c8be374db in g_main_context_dispatch ()
   from /lib64/libglib-2.0.so.0
#4  0x0000003c8be3acbd in ?? () from /lib64/libglib-2.0.so.0
#5  0x0000003c8be3b1ed in g_main_loop_run () from /lib64/libglib-2.0.so.0
#6  0x0000000000419126 in main (argc=1, argv=0x7fffbf2b49f8)
    at tracker-main.c:354
(gdb)


In tracker_indexer_module_file_iter_contents(), file->data access can't work
because file is NULL.


(gdb) frame 2
#2  0x000000000041590b in process_func (data=0x1173890)
    at tracker-indexer.c:1820
1820                        if (process_file (indexer, path)) {
(gdb) print *path
$6 = {module = 0x29e3900, file = 0x0, module_name = 0x1fee960 "`>\036\001"}
(gdb)



Right, so that PathInfo instance 'path' is obviously not a good one.

The bugfix will be finding out why the instance is foobar, and then
fixing this.

If you can further investigate as to how this 'path' instance came to
be, you'd help us a lot with finding this.

But thanks for the help already. It's a very valuable bug report.


-- 
Philip Van Hoof, freelance software developer
home: me at pvanhoof dot be 
gnome: pvanhoof at gnome dot org 
http://pvanhoof.be/blog
http://codeminded.be







[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]