Chapter 9. Miscellaneous

Table of Contents
9.1. Reporting bugs
9.2. Using libdpsearch library
9.3. Database schema

9.1. Reporting bugs

When reporting bugs, please specify DataparkSearch version and provide us 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 at DataparkSearch web site. Please do not send reports to mailing list or to personal authors addresses!

9.1.1. Currently known bugs

Use DataparSearch Bug Reporting System to view active and fixed bug statistics. As well, you can use this system to submit new bug-reports and proposals for new feature or improvements

9.1.2. Core dump reports

If indexer or search.cgi die during their work and produce core, it would be very helpful to send us gdb (The GNU Debugger) output. To do this, please make the following steps. Make sure you have DataparkSearch built with --with-debug option for configure. If not, please rebuild it with this option and repeat the command leads to core dump. Then, e.g. your binary is "indexer" and core file name is indexer.core (or may be just core on some platforms).

Run GNU Debugger with 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/
Reading symbols from /usr/libexec/
#0  0x80483f3 in main () at indexer.c:4
4               printf("%d",0/0);

Then type thread apply all backtrace command:

(gdb) thread apply all bt
#0  0x80483f3 in main () at indexer.c:4
#1  0x804837d in _start ()

Send us either first and second outputs or just a screenshot of gdb session.