Seth Woolley's Man Viewer

perlbug(1) - perlbug - how to submit bug reports on Perl - man 1 perlbug

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

PERLBUG(1)             Perl Programmers Reference Guide             PERLBUG(1)

       perlbug - how to submit bug reports on Perl

       perlbug [ -v ] [ -a address ] [ -s subject ] [ -b body | -f inputfile ]
       [ -F outputfile ] [ -r returnaddress ] [ -e editor ] [ -c adminad-
       dress | -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(1,8) them.

       If you have found a bug with a non-standard port (one that was not part
       of the standard distribution), a binary distribution, 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(2,8) to send(2,n) mail(1,8) that perlbug recognizes), you may have to
       compose your own report, and email it to  You might
       find the -d option useful to get summary information in(1,8) that case.

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

       What version(1,3,5) of Perl you are running?
           Type "perl -v" at the command line to find out.

       Are you running the latest released version(1,3,5) of perl?
           Look at to find out.  If it is not the latest
           released version(1,3,5), get that one and see whether your bug has been
           fixed.  Note that bug reports about old versions of Perl, espe-
           cially those prior to the 5.0 release, are likely to fall upon deaf
           ears.  You are on your own if(3,n) 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 docu-
           mented features in(1,8) Perl.  Make sure the behavior you are witnessing
           doesn't fall under that category, by glancing through the documen-
           tation that comes with Perl (we'll admit this is no mean task,
           given the sheer volume of it all, but at least have a look(1,8,3 Search::Dict) at the
           sections that seem relevant).

           Be aware of the familiar traps that perl programmers of various
           hues fall into.  See perltrap.

           Check in(1,8) perldiag to see what any Perl error(8,n) message(s) mean.  If
           message isn't in(1,8) perldiag, it probably isn't generated by Perl.
           Consult your operating system documentation instead.

           If you are on a non-UNIX platform check also perlport, as some fea-
           tures may be unimplemented or work differently.

           Try to study the problem under the Perl debugger, if(3,n) 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(3,n) no one can duplicate 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, modules, or
           libraries; runs on most platforms unimpeded; and is self-document-

           A good test case is almost always a good candidate to be on the
           perl test suite.  If you have the time(1,2,n), consider making your test
           case so that it will readily fit into the standard test suite.

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

           If you get a core dump (or equivalent), you may use a debugger
           (dbx, gdb, etc) to produce a stack trace(3x,n,3x _nc_tracebits) to include in(1,8) the bug
           report.  NOTE: unless your Perl has been compiled with debug info(1,5,n)
           (often -g), the stack trace(3x,n,3x _nc_tracebits) 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(1,5,n) and reproduce the dump and the stack trace.

       Can you describe the bug in(1,8) plain English?
           The easier it is to understand a reproducible bug, the more likely
           it will be fixed.  Anything you can provide 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 defi-
           nitely be fixed.  Use the "diff" program to generate your patches
           ("diff" is being maintained by the GNU folks as part of the diffu-
           tils 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 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 so-called context or uni-
           fied diff).  Make sure the patch is not reversed (the first argu-
           ment to diff is typically the original file(1,n), the second argument
           your changed file(1,n)).  Make sure you test your patch by applying it
           with the "patch" program before you send(2,n) it on its way.  Try to
           follow the same style as the code you are trying to patch.  Make
           sure your patch really does work ("make test", if(3,n) the thing you're
           patching supports it).

       Can you use "perlbug" to submit the report?
           perlbug will, amongst other things, ensure your report includes
           crucial information about your version(1,3,5) of perl.  If "perlbug" is
           unable to mail(1,8) your report after you have typed it in(1,8), you may have
           to compose the message yourself, add the output produced by "perl-
           bug -d" and email it to  If, for some reason, you
           cannot run "perlbug" at all on your system, be sure to include the
           entire output produced by running "perl -V" (note the uppercase V).

           Whether you use "perlbug" or send(2,n) 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(1,8) your code, or even to get no reply at all.  The Perl maintainers are
       busy folks, so if(3,n) your problem is a small one or if(3,n) 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(1,n) in(1,8) any development releases since the time(1,2,n) you sub-
       mitted the bug, and encourage the maintainers with kind words (but
       never any flames!).  Feel free to resend your bug report if(3,n) the next
       released version(1,3,5) of perl comes out and your bug is still present.

       -a      Address to send(2,n) the report to.  Defaults to

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

       -b      Body of the report.  If not included on the command line, or in(1,8)
               a file(1,n) with -f, you will get a chance to edit the message.

       -C      Don't send(2,n) copy to administrator.

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

       -d      Data mode (the default if(3,n) you redirect or pipe(2,8) 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.

       -f      File containing the body of the report.  Use this to quickly
               send(2,n) a prepared message.

       -F      File to output the results to instead of sending as an email.
               Useful particularly when running perlbug on a machine with no
               direct internet connection.

       -h      Prints a brief summary of the options.

       -ok     Report successful build on this system to perl porters. Forces
               -S and -C. Forces and supplies values for -s and -b. Only
               prompts for a return address if(3,n) 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(3,n) this system is less(1,3) than 60 days old.

       -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(3,n) 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(3,n) this system is
               less(1,3) than 60 days old.

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

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

       -S      Send without asking for confirmation.

       -s      Subject to include with the message.  You will be prompted if(3,n)
               you don't supply one on the command line.

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

       -v      Include verbose configuration data in(1,8) the report.

       Kenneth Albanowski (<>), subsequently doctored by
       Gurusamy Sarathy (<>), Tom Christiansen
       (<>), Nathan Torkington (<>), Charles F.
       Randall (<>), Mike Guy (<>), Dominic Dunlop
       (<>), Hugo van der Sanden (<<gt>), Jarkko
       Hietaniemi (<>), Chris Nandor (<>), Jon Orwant
       (<>, and Richard Foley (<>).

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

       None known (guess what must have been used to report them?)

perl v5.8.5                       2004-09-17                        PERLBUG(1)

References for this manual (incoming links)