• Antelope Release 5.10 Linux CentOS release 7.6.1810 (Core) 3.10.0 2020-05-12

 

NAME

bugs - reporting Antelope problems

DESCRIPTION

At BRTT, we want to hear about any problems you encounter with Antelope software. Depending on the problem and the program(s) involved, we may be able to suggest a solution or workaround immediately. In other cases, we may need to provide a patch.

If a program dies with a segmentation fault, bus error, or floating point error, we particularly want to hear about it. This should not happen (except if you are deleting rows from a database table while another program is using the same table).

To provide any support, however, we need to have a clear description of the problem, so that we can reproduce it at our offices. This man page makes some suggestions for problem solving and reporting.

First steps

When you encounter a problem, first make sure it's a problem.

Gather the information

We need to be able to reproduce the problem in order to find and fix it. Therefore, we want to see at least all of the following:

Sometimes it's difficult to collect all the right files. Antelope includes a number of snapshot programs designed to collect a bunch of information; these may help you report a bug. The programs are:

A snapshot is not by itself an error report. You still must tell us

Send us email

Once you've collected the information, and written a description of what happened, send it to us at support@brtt.com. We'll respond as quickly as we can.

Do not send problem reports to individual email addresses at BRTT: they will not be answered. To receive a response, only use support@brtt.com. Requests sent to support@brtt.com are read by multiple people and will be responded to in a timely manner.

EXAMPLE

Here are some examples of what not to do:

Exactly how doesn't it work? What have you tried? What was the input and output?

We periodically get these kinds of questions, where the first puzzle is to figure out what the author thought was wrong. We often lack the context that may make the problem obvious to you. In addition to showing us the command and the output, please explain what's wrong with the output, and send us the input data if you can, so that we can reproduce the problem.

SEE ALSO

reporting(5)
http://catb.org/~esr/faqs/smart-questions.html

BUGS AND CAVEATS

Writing bug reports is hard work.

BUG MISCOMMUNICATION

Take the advice above and avoid the problems below.

Pilots fill out a form after every flight about any problems encountered.

Mechanics in turn inform the pilots what measures were taken.

Here are several reports, and the resulting actions.

AUTHOR

Daniel Quinlan
Printer icon