-
Notifications
You must be signed in to change notification settings - Fork 1
/
chicken-bug.1
61 lines (46 loc) · 1.45 KB
/
chicken-bug.1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
.\" dummy line
.TH CHICKEN-BUG 1 "19 Sep 2001"
.SH NAME
chicken-bug \- generates a bug report from user input
.SH SYNOPSIS
.B chicken-bug
[
.I filename
|
.I OPTION ...
]
.SH OPTIONS
.TP
.B \-help
Show usage information.
.TP
.B \-to-stdout
Write bug report to standard output instead of writing it to a file.
.TP
.B \-
Read user input from standard input, even if files are given on the command line.
.SH DESCRIPTION
.I chicken-bug
generates a bug report file that collects user-input, optional
files and system information obtained from the installed CHICKEN
executables and libraries. Non-option arguments given on the command line
are inserted into the bug report. If no option is given, or if
.B \-
has been passed on the command line, then a description of the problem
is read from standard input, until EOF (CTRL-D) or a line consisting only
of "." (period) is read.
The bug report will be written to a file in the current directory,
which should be sent to CHICKEN maintainers as it contains various
useful bits of information that make it easier to classify the
problem described.
Bug reports should be as detailed as possible. It is also very helpful
to include code that reproduces the problem. The more detailed the input
and the more thorough the description is, the easier you make it for
the CHICKEN developers to help you.
.SH BUGS
Submit bug reports by e-mail to
.I chicken-janitors@nongnu.org
.SH AUTHOR
The CHICKEN Team.
.SH SEE ALSO
.BR chicken(1)