Back to mnoGoSearch site


mnoGoSearch 3.2.43 reference manual: Full-featured search engine software
PrevNext

Chapter 9. Miscellaneous

Table of Contents
Reporting bugs
Using libmnogosearch library
MySQL fulltext parser plugin
Database schema

Reporting bugs

When reporting bugs, please specify the mnoGoSearch version you are using and provide as much information about your problem as possible. Such information as your platform and OS details, database version, database statistics like number of URLs in database or probably count of records in different tables would be very helpful to find and fix possible bugs.

Please, submit bug reports using our Bug Reporting System found at mnoGoSearch web site at http://mnogosearch.org/bugs/. Please do not send reports to the developers list or to private authors addresses!

Currently known bugs

Use mnoGoSearch Bug Reporting System to view active and fixed bugs statistics. The Bug Reporting System can be fount at http://mnogosearch.org/bugs/

Core dump reports

If the indexer or search.cgi die during their work and produce a core, it would be very helpful to send us gdb (The GNU Debugger) output. To do this, please make the following steps. E.g. your binary is "indexer" and the core file name is indexer.core (or may be just core on some platforms).

Run GNU Debugger with the executable as the first argument and with core file as the second:

gdb indexer indexer.core

Some information about the crash location will appear:


Core was generated by `indexer'.
Program terminated with signal 8, Floating point exception.
Reading symbols from /usr/lib/libc.so.3...done.
Reading symbols from /usr/libexec/ld-elf.so.1...done.
#0  0x80483f3 in main () at indexer.c:4
4               printf("%d",0/0);

Then type backtrace command:


(gdb) backtrace
#0  0x80483f3 in main () at indexer.c:4
#1  0x804837d in _start ()

Send us either the first and second outputs or just a screen-shot of the gdb session.