DataparkSearch Engine 4.26 reference manual: The Web searching software
Prev |  | Next

# Chapter 9. Miscellaneous

# 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!

## 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. 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/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 first and second outputs or just a screenshot of gdb session.

## Donations

If you use DataparkSearch and like it, or perhaps your company makes money from DataparkSearch or related activities, why not support the project with a donation (at Kagi)? We need about US$400/month to support DataparkSearch development.

Prev | Home | Next
Fuzzy search |  | Using `libdpsearch` library