There are total of 3 bug type categories, the procedure depends on
what kind of bug you are dealing with. With all bug types you should
always append the following information to E-mails sent to
equ@equnet.org

- oer+MySQL version
- Operating System & version (type "uname -a" in console)

With "Operational bug" and "Fatal bug" bug types also append

- MySQL version
- Database dump without data (mysqldump -d)

Packaging, configure, compilation & installation bugs
-----------------------------------------------------

If there is something wrong with the oer+MySQL package, send a E-mail
to equ@equnet.org with subject "oer+MySQL bug report: packaging". In
the message part let me know what the problem is.

If you think you have found a problem with "configure" send a E-mail
to equ@equnet.org with subject "oer+MySQL bug report: configure" and
attach console output of configure run, config.log and config.status
to the E-mail.

If there is a compiling or installation bug send the console output and
pre_install.log to equ@equnet.org with subject
"oer+MySQL bug report: compile & installation".

Operational bug
---------------

If you think oer+MySQL missbehaves in some way but doesn't crash, you
will have to enable logging of console output and dump the contents of
table "output" with mysqldump. Enable the logging of output messages
by setting the global flag "l". Then configure & compile oer+MySQL
with "--enable-debug". Then start oer+MySQL with 
"./oer+MySQL -c -d 9 -o". Dump the "output" table with mysqldump
and send the database dump via E-mail to equ@equnet.org with the
subject "oer+MySQL bug report: operational".

Fatal bug
---------

If oer+MySQL terminates unexpectedly ("crashes") proceed as follows.

First off, configure & compile oer+MySQL with the following options:

--enable-debug --disable-opt

Then make sure that your command shell allows core dumps:

limit coredumpsize 10000 (bash)
ulimit -c 10000          (csh/tcsh)

Just like with operational bugs you will have to enable logging of
console output and dump the table "output" with mysqldump. Enable the
logging of output messages by setting the global flag "l".  Then start
oer+MySQL with "./oer+MySQL -c -d 9 -o". Dump the "output" table with
mysqldump. After oer+MySQL has "crashed" start gdb by writing
"gdb oer+MySQL core" and then get a backtrace by writing "bt" and
pressing enter. Send both, the database dump and the backtrace to
equ@equnet.org with the subject "oer+MySQL bug report: fatal".

Other types of bugs
------------------- 

If the bug/problem you are dealing with doesn't belong to any of the
above bug categories, send a E-mail to equ@equnet.org with subject
"oer+MySQL bug report: unknown" and describe the bug/problem.

        Thank you in advance
