Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Bread for the World

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 86 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       perlbug [ -v ] [ -a address ] [ -s subject ]
       [ -b body | -f inputfile ] [ -F outputfile ] [ -r retur­
       naddress ] [ -e editor ] [ -c adminaddress | -C ] [ -S ]
       [ -t ]  [ -d ]  [ -A ]  [ -h ]

       perlbug [ -v ] [ -r returnaddress ]
        [ -A ] [ -ok | -okay | -nok | -nokay ]


       A program to help generate bug reports about perl or the
       modules that come with it, and mail them.

       If you have found a bug with a non-standard port (one that
       was not part of the standard distribution), a binary dis­
       tribution, or a non-standard module (such as Tk, CGI,
       etc), then please see the documentation that came with
       that distribution to determine the correct place to report

       "perlbug" is designed to be used interactively. Normally
       no arguments will be needed.  Simply run it, and follow
       the prompts.

       If you are unable to run perlbug (most likely because you
       don't have a working setup to send mail that perlbug rec­
       ognizes), you may have to compose your own report, and
       email it to perlbug@perl.org.  You might find the -d
       option useful to get summary information in that case.

       In any case, when reporting a bug, please make sure you
       have run through this checklist:

       What version of Perl you are running?
           Type "perl -v" at the command line to find out.

       Are you running the latest released version of perl?
           Look at http://www.perl.com/ to find out.  If it is
           not the latest released version, get that one and see
           whether your bug has been fixed.  Note that bug
           reports about old versions of Perl, especially those
           prior to the 5.0 release, are likely to fall upon deaf
           ears.  You are on your own if you continue to use
           perl1 .. perl4.

       Are you sure what you have is a bug?
           A significant number of the bug reports we get turn
           out to be documented features in Perl.  Make sure the
           behavior you are witnessing doesn't fall under that
           category, by glancing through the documentation that
           comes with Perl (we'll admit this is no mean task,
           given the sheer volume of it all, but at least have a
           Try to study the problem under the Perl debugger, if
           necessary.  See perldebug.

       Do you have a proper test case?
           The easier it is to reproduce your bug, the more
           likely it will be fixed, because if no one can dupli­
           cate the problem, no one can fix it.  A good test case
           has most of these attributes: fewest possible number
           of lines; few dependencies on external commands, mod­
           ules, or libraries; runs on most platforms unimpeded;
           and is self-documenting.

           A good test case is almost always a good candidate to
           be on the perl test suite.  If you have the time, con­
           sider making your test case so that it will readily
           fit into the standard test suite.

           Remember also to include the exact error messages, if
           any.  "Perl complained something" is not an exact
           error message.

           If you get a core dump (or equivalent), you may use a
           debugger (dbx, gdb, etc) to produce a stack trace to
           include in the bug report.  NOTE: unless your Perl has
           been compiled with debug info (often -g), the stack
           trace is likely to be somewhat hard to use because it
           will most probably contain only the function names and
           not their arguments.  If possible, recompile your Perl
           with debug info and reproduce the dump and the stack

       Can you describe the bug in plain English?
           The easier it is to understand a reproducible bug, the
           more likely it will be fixed.  Anything you can pro­
           vide by way of insight into the problem helps a great
           deal.  In other words, try to analyze the problem (to
           the extent you can) and report your discoveries.

       Can you fix the bug yourself?
           A bug report which includes a patch to fix it will
           almost definitely be fixed.  Use the "diff" program to
           generate your patches ("diff" is being maintained by
           the GNU folks as part of the diffutils package, so you
           should be able to get it from any of the GNU software
           repositories).  If you do submit a patch, the cool-
           dude counter at perlbug@perl.org will register you as
           a savior of the world.  Your patch may be returned
           with requests for changes, or requests for more
           detailed explanations about your fix.

           Here are some clues for creating quality patches: Use
           the -c or -u switches to the diff program (to create a
           after you have typed it in, you may have to compose
           the message yourself, add the output produced by
           "perlbug -d" and email it to perlbug@perl.org.  If,
           for some reason, you cannot run "perlbug" at all on
           your system, be sure to include the entire output pro­
           duced by running "perl -V" (note the uppercase V).

           Whether you use "perlbug" or send the email manually,
           please make your Subject line informative.  "a bug"
           not informative.  Neither is "perl crashes" nor
           "HELP!!!".  These don't help.  A compact description
           of what's wrong is fine.

       Having done your bit, please be prepared to wait, to be
       told the bug is in your code, or even to get no reply at
       all.  The Perl maintainers are busy folks, so if your
       problem is a small one or if it is difficult to understand
       or already known, they may not respond with a personal
       reply.  If it is important to you that your bug be fixed,
       do monitor the "Changes" file in any development releases
       since the time you submitted the bug, and encourage the
       maintainers with kind words (but never any flames!).  Feel
       free to resend your bug report if the next released ver­
       sion of perl comes out and your bug is still present.


       -a      Address to send the report to.  Defaults to perl­

       -A      Don't send a bug received acknowledgement to the
               reply address.  Generally it is only a sensible to
               use this option if you are a perl maintainer
               actively watching perl porters for your message to

       -b      Body of the report.  If not included on the com­
               mand line, or in a file with -f, you will get a
               chance to edit the message.

       -C      Don't send copy to administrator.

       -c      Address to send copy of report to.  Defaults to
               the address of the local perl administrator
               (recorded when perl was built).

       -d      Data mode (the default if you redirect or pipe
               output).  This prints out your configuration data,
               without mailing anything.  You can use this with
               -v to get more complete data.

       -e      Editor to use.

               Honors return address specified with -r.  You can
               use this with -v to get more complete data.   Only
               makes a report if this system is less than 60 days

       -okay   As -ok except it will report on older systems.

       -nok    Report unsuccessful build on this system.  Forces
               -C.  Forces and supplies a value for -s, then
               requires you to edit the report and say what went
               wrong.  Alternatively, a prepared report may be
               supplied using -f.  Only prompts for a return
               address if it cannot guess it (for use with make).
               Honors return address specified with -r.  You can
               use this with -v to get more complete data.  Only
               makes a report if this system is less than 60 days

       -nokay  As -nok except it will report on older systems.

       -r      Your return address.  The program will ask you to
               confirm its default if you don't use this option.

       -S      Send without asking for confirmation.

       -s      Subject to include with the message.  You will be
               prompted if you don't supply one on the command

       -t      Test mode.  The target address defaults to perl­

       -v      Include verbose configuration data in the report.


       Kenneth Albanowski (<kjahds@kjahds.com>), subsequently
       doctored by Gurusamy Sarathy (<gsar@activestate.com>), Tom
       Christiansen (<tchrist@perl.com>), Nathan Torkington
       (<gnat@frii.com>), Charles F. Randall (<cfr@pobox.com>),
       Mike Guy (<mjtg@cam.a.uk>), Dominic Dunlop (<domo@com­
       puter.org>), Hugo van der Sanden (<hv@crypt.org<gt>),
       Jarkko Hietaniemi (<jhi@iki.fi>), Chris Nandor
       (<pudge@pobox.com>), Jon Orwant (<orwant@media.mit.edu>,
       and Richard Foley (<richard@rfi.net>).


       perl(1), perldebug(1), perldiag(1), perlport(1), perl­
       trap(1), diff(1), patch(1), dbx(1), gdb(1)


       None known (guess what must have been used to report

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =




Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can choose larger fonts by selecting a different themes.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.11 Seconds