Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   44335 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

CHICKEN-BUG(1)							CHICKEN-BUG(1)

NAME
       chicken-bug - generates a bug report from user input

SYNOPSIS
       chicken-bug [ filename | OPTION ...  ]

OPTIONS
       -help  Show usage information.

       -to-stdout
	      Write  bug  report to standard output instead of writing it to a
	      file.

       -      Read user input from standard input, even if files are given  on
	      the command line.

DESCRIPTION
       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 - 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  con‐
       sisting 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 use‐
       ful  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.

BUGS
       Submit bug reports by e-mail to chicken-janitors@nongnu.org

AUTHOR
       The CHICKEN Team.

SEE ALSO
       chicken(1)

				  19 Sep 2001			CHICKEN-BUG(1)

Vote for polarhome