Section: Perl Programmers Reference Guide (1)
perlbug [ -v ] [ -a address ] [ -s subject ] [ -b body | -f inputfile ] [ -F outputfile ] [ -r returnaddress ] [ -e editor ] [ -c adminaddress | -C ] [ -S ] [ -t ] [ -d ] [ -A ] [ -h ] [ -T ]
perlbug [ -v ] [ -r returnaddress ]
[ -A ] [ -ok | -okay | -nok | -nokay ]
This program is designed to help you generate and send bug reports (and thank-you notes) about perl5 and the modules which ship with it.
In most cases, you can just run it interactively from a command line without any special arguments and follow the prompts.
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-core module (such as Tk, DBI, etc), then please see the documentation that came with that distribution to determine the correct place to report bugs.
If you are unable to send your report using perlbug (most likely because your system doesn't have a way to send mail that perlbug recognizes), you may be able to use this tool to compose your report and save it to a file which you can then send to [email protected] using your regular mail client.
In extreme cases, perlbug may not work well enough on your system to guide you through composing a bug report. In those cases, you may be able to use perlbug -d to get system configuration information to include in a manually composed bug report to [email protected].
When reporting a bug, please run through this checklist:
"perl -v"at the command line to find out.:
Note that reports about bugs in old versions of Perl, especially those which indicate you haven't also tested the current stable release of Perl, are likely to receive less attention from the volunteers who build and maintain Perl than reports about bugs in the current release.
This tool isn't appropriate for reporting bugs in any version prior to Perl 5.0.
Given the sheer volume of Perl documentation, this isn't a trivial undertaking, but if you can point to documentation that suggests the behaviour you're seeing is wrong, your issue is likely to receive more attention. You may want to start with perldoc perltrap for pointers to common traps that new (and experienced) Perl programmers run into.
If you're unsure of the meaning of an error message you've run across, perldoc perldiag for an explanation. If the message isn't in perldiag, it probably isn't generated by Perl. You may have luck consulting your operating system documentation instead.
If you are on a non-UNIX platform perldoc perlport, as some features may be unimplemented or work differently.
You may be able to figure out what's going wrong using the Perl debugger. For information about how to use the debugger perldoc perldebug.
A good test case has most of these attributes: short, simple code; few dependencies on external commands, modules, or libraries; no platform-dependent code (unless it's a platform-specific bug); clear, simple documentation.
A good test case is almost always a good candidate to be included in Perl's test suite. If you have the time, consider writing your test case so that it can be easily included into the standard test suite.
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 crash and the stack trace.
"-p"option. When sending a patch, create it using
"git format-patch"if possible, though a unified diff created with
"diff -pu"will do nearly as well.
Your patch may be returned with requests for changes, or requests for more detailed explanations about your fix.
Here are a few hints for creating high-quality patches:Make sure the patch is not reversed (the first argument to diff is typically the original file, the second argument your changed file). Make sure you test your patch by applying it with
"git am"or the
"patch"program before you send 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 the thing you're patching is covered by Perl's test suite).
"perlbug"is unable to mail your report 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 [email protected]. 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).
"perlbug"or send the email manually, please make your Subject line informative. ``a bug is not informative. Neither is ``perl crashes nor is ``HELP!!!''. These don't help. A compact description of what's wrong is fine.
"-T"option, or by invoking the program as
"perlthanks". Thank-you notes are good. It makes people smile.:
Having done your bit, please be prepared to wait, to be told the bug is in your code, or possibly to get no reply at all. The volunteers who maintain Perl are busy folks, so if your problem is an obvious bug in your own code, is difficult to understand or is a duplicate of an existing report, you may not receive a personal reply.
If it is important to you that your bug be fixed, do monitor the [email protected] mailing list (mailing lists are moderated, your message may take a while to show up) and the commit logs to development versions of Perl, and encourage the maintainers with kind words or offers of frosty beverages. (Please do be kind to the maintainers. Harassing or flaming them is likely to have the opposite effect of the one you want.)
Feel free to update the ticket about your bug on http://rt.perl.org if a new version of Perl is released and your bug is still present.
Kenneth Albanowski (<[email protected]>), subsequently doctored by Gurusamy Sarathy (<[email protected]>), Tom Christiansen (<[email protected]>), Nathan Torkington (<[email protected]>), Charles F. Randall (<[email protected]>), Mike Guy (<[email protected]>), Dominic Dunlop (<[email protected]>), Hugo van der Sanden (<[email protected]>), Jarkko Hietaniemi (<[email protected]>), Chris Nandor (<[email protected]>), Jon Orwant (<[email protected]>, Richard Foley (<[email protected]>), Jesse Vincent (<[email protected]>), and Craig A. Berry (<[email protected]>).
None known (guess what must have been used to report them?)
Tutoriais de Tecnologia Web