If you experience problems with the indexing process, there are several ways
you can go about reporting problems.

One is try your indexing with logging, and to report the results (or
tail) of the log to gnome bugzilla using bug-buddy.
Logging can be done by setting one of the following environment
variables:

1.  MEDUSA_INDEX_DEBUG   -- list all indexing and  text indexing operations
2.  MEDUSA_INDEX_LOG_ABBREVIATE -- list all files indexed so far
3.  MEDUSA_INDEX_LOG_ERRORS -- log errors (not very useful currently)

If you are using the medusa-restart script, your logging information is
stored in /tmp/medusa-indexd-log and /tmp/medusa-searchd-log.

----

You can also run the indexer in gdb and report stack traces and
looping behavior to the same email addresses as above.  

Here are ways to run the indexer or search daemon by hand, under gdb.
To run the search daemon in debug mode, (so that it doesn't fork) you should
use the --debug flag.

[rebecka@minerva medusa] cd-medusa
[rebecka@minerva medusa] su
Password:
[root@minerva medusa] gdb /gnome/bin/medusa-searchd 
(gdb) set args --debug
-or-
[root@minerva medusa] gdb /gnome/bin/medusa-indexd


This is an alternative way to the first.

[rebecka@minerva medusa] su
Password:
[root@minerva medusa] eazel-env-set-gnome-no-cvs
[root@minerva medusa] gdb /gnome/bin/medusa-searchd
(gdb) set args --debug


To investigate problems about an already running search or 
indexing daemon, you can attach to a running daemon process.
You can locate the process using the UNIX command

ps -ax

Once the process number is located, you can attach gdb to
the process by listing the process number of the running 
process after its name.  You must have permission to do this,
so you should follow the directions above to become
root and set up your environment correctly.

For example

18136     medusa-indexd

gdb /gnome/bin/medusa-indexd 18136
