4 use File::Basename qw(&basename &dirname);
6 use File::Spec::Functions;
8 # List explicitly here the variables you want Configure to
9 # generate. Metaconfig only looks for shell variables, so you
10 # have to mention them as if they were shell variables, not
11 # %Config entries. Thus you write
13 # to ensure Configure will look for $Config{startperl}.
16 # This forces PL files to create target in same directory as PL file.
17 # This is so that make depend always knows where to find PL derivatives.
20 $file = basename($0, '.PL');
21 $file .= '.com' if $^O eq 'VMS';
23 open OUT, ">$file" or die "Can't create $file: $!";
25 # extract patchlevel.h information
27 open PATCH_LEVEL, "<" . catfile(updir, "patchlevel.h")
28 or die "Can't open patchlevel.h: $!";
30 my $patchlevel_date = (stat PATCH_LEVEL)[9];
32 while (<PATCH_LEVEL>) {
33 last if $_ =~ /^\s*static\s+char.*?local_patches\[\]\s*=\s*{\s*$/;
37 while (<PATCH_LEVEL>) {
43 push @patches, $_ unless $_ eq 'NULL';
45 my $patch_desc = "'" . join("',\n '", @patches) . "'";
46 my $patch_tags = join "", map /(\S+)/ ? "+$1 " : (), @patches;
48 close(PATCH_LEVEL) or die "Error closing patchlevel.h: $!";
50 # TO DO (prehaps): store/embed $Config::config_sh into perlbug. When perlbug is
51 # used, compare $Config::config_sh with the stored version. If they differ then
52 # append a list of individual differences to the bug report.
55 print "Extracting $file (with variable substitutions)\n";
57 # In this section, perl variables will be expanded during extraction.
58 # You can use $Config{...} to use Configure variables.
60 my $extract_version = sprintf("v%vd", $^V);
62 print OUT <<"!GROK!THIS!";
64 eval 'exec $Config{perlpath} -S \$0 \${1+"\$@"}'
65 if \$running_under_some_shell;
67 my \$config_tag1 = '$extract_version - $Config{cf_time}';
69 my \$patchlevel_date = $patchlevel_date;
70 my \$patch_tags = '$patch_tags';
76 # In the following, perl variables are not expanded during extraction.
78 print OUT <<'!NO!SUBS!';
81 use File::Spec; # keep perlbug Perl 5.005 compatible
88 eval "use Mail::Send;";
89 $::HaveSend = ($@ eq "");
90 eval "use Mail::Util;";
91 $::HaveUtil = ($@ eq "");
96 # Changed in 1.06 to skip Mail::Send and Mail::Util if not available.
97 # Changed in 1.07 to see more sendmail execs, and added pipe output.
98 # Changed in 1.08 to use correct address for sendmail.
99 # Changed in 1.09 to close the REP file before calling it up in the editor.
100 # Also removed some old comments duplicated elsewhere.
101 # Changed in 1.10 to run under VMS without Mail::Send; also fixed
102 # temp filename generation.
103 # Changed in 1.11 to clean up some text and removed Mail::Send deactivator.
104 # Changed in 1.12 to check for editor errors, make save/send distinction
105 # clearer and add $ENV{REPLYTO}.
106 # Changed in 1.13 to hopefully make it more difficult to accidentally
108 # Changed in 1.14 to make the prompts a little more clear on providing
109 # helpful information. Also let file read fail gracefully.
110 # Changed in 1.15 to add warnings to stop people using perlbug for non-bugs.
111 # Also report selected environment variables.
112 # Changed in 1.16 to include @INC, and allow user to re-edit if no changes.
113 # Changed in 1.17 Win32 support added. GSAR 97-04-12
114 # Changed in 1.18 add '-ok' option for reporting build success. CFR 97-06-18
115 # Changed in 1.19 '-ok' default not '-v'
116 # add local patch information
117 # warn on '-ok' if this is an old system; add '-okay'
118 # Changed in 1.20 Added patchlevel.h reading and version/config checks
119 # Changed in 1.21 Added '-nok' for reporting build failure DFD 98-05-05
120 # Changed in 1.22 Heavy reformatting & minor bugfixes HVDS 98-05-10
121 # Changed in 1.23 Restore -ok(ay): say 'success'; don't prompt
122 # Changed in 1.24 Added '-F<file>' to save report HVDS 98-07-01
123 # Changed in 1.25 Warn on failure to open save file. HVDS 98-07-12
124 # Changed in 1.26 Don't require -t STDIN for -ok. HVDS 98-07-15
125 # Changed in 1.27 Added Mac OS and File::Spec support CNANDOR 99-07-27
126 # Changed in 1.28 Additional questions for Perlbugtron RFOLEY 20.03.2000
127 # Changed in 1.29 Perlbug(tron): auto(-ok), short prompts RFOLEY 05-05-2000
128 # Changed in 1.30 Added warnings on failure to open files MSTEVENS 13-07-2000
129 # Changed in 1.31 Add checks on close().Fix my $var unless. TJENNESS 26-07-2000
130 # Changed in 1.32 Use File::Spec->tmpdir TJENNESS 20-08-2000
131 # Changed in 1.33 Don't require -t STDOUT for -ok.
133 # TODO: - Allow the user to re-name the file on mail failure, and
134 # make sure failure (transmission-wise) of Mail::Send is
138 my( $file, $usefile, $cc, $address, $perlbug, $testaddress, $filename,
139 $subject, $from, $verbose, $ed, $outfile, $Is_MacOS, $category, $severity,
140 $fh, $me, $Is_MSWin32, $Is_VMS, $msg, $body, $andcc, %REP, $ok);
142 my $perl_version = $^V ? sprintf("v%vd", $^V) : $];
144 my $config_tag2 = "$perl_version - $Config{cf_time}";
148 if ($::opt_h) { Help(); exit; }
149 if ($::opt_d) { Dump(*STDOUT); exit; }
150 if (!-t STDIN && !($ok and not $::opt_n)) {
152 Please use perlbug interactively. If you want to
153 include a file, you can use the -f switch.
159 Edit() unless $usefile || ($ok and not $::opt_n);
165 sub ask_for_alternatives { # (category|severity)
171 'opts' => [qw(core docs install library utilities)], # patch, notabug
176 'opts' => [qw(critical high medium low wishlist none)], # zero
179 die "Invalid alternative($name) requested\n" unless grep(/^$name$/, keys %alts);
182 $alt = $alts{$name}{'ok'};
184 my @alts = @{$alts{$name}{'opts'}};
186 Please pick a \u$name from the following:
194 die "Invalid $name: aborting.\n";
196 print "Please enter a \u$name [$alts{$name}{'default'}]: ";
199 if ($alt =~ /^\s*$/) {
200 $alt = $alts{$name}{'default'};
202 } while !((($alt) = grep(/^$alt/i, @alts)));
208 # -------- Setup --------
210 $Is_MSWin32 = $^O eq 'MSWin32';
211 $Is_VMS = $^O eq 'VMS';
212 $Is_MacOS = $^O eq 'MacOS';
214 @ARGV = split m/\s+/,
215 MacPerl::Ask('Provide command-line args here (-h for help):')
216 if $Is_MacOS && $MacPerl::Version =~ /App/;
218 if (!getopts("Adhva:s:b:f:F:r:e:SCc:to:n:")) { Help(); exit; };
220 # This comment is needed to notify metaconfig that we are
221 # using the $perladmin, $cf_by, and $cf_time definitions.
223 # -------- Configuration ---------
226 $perlbug = 'perlbug@perl.org';
229 $testaddress = 'perlbug-test@perl.com';
232 $address = $::opt_a || ($::opt_t ? $testaddress : $perlbug);
234 # Users address, used in message and in Reply-To header
235 $from = $::opt_r || "";
237 # Include verbose configuration information
238 $verbose = $::opt_v || 0;
240 # Subject of bug-report message
241 $subject = $::opt_s || "";
244 $usefile = ($::opt_f || 0);
246 # File to send as report
247 $file = $::opt_f || "";
250 $outfile = $::opt_F || "";
253 $body = $::opt_b || "";
256 $ed = $::opt_e || $ENV{VISUAL} || $ENV{EDITOR} || $ENV{EDIT}
257 || ($Is_VMS && "edit/tpu")
258 || ($Is_MSWin32 && "notepad")
262 # Not OK - provide build failure template by finessing OK report
264 if (substr($::opt_n, 0, 2) eq 'ok' ) {
265 $::opt_o = substr($::opt_n, 1);
272 # OK - send "OK" report for build on this system
275 if ($::opt_o eq 'k' or $::opt_o eq 'kay') {
276 my $age = time - $patchlevel_date;
277 if ($::opt_o eq 'k' and $age > 60 * 24 * 60 * 60 ) {
278 my $date = localtime $patchlevel_date;
280 "perlbug -ok" and "perlbug -nok" do not report on Perl versions which
281 are more than 60 days old. This Perl version was constructed on
282 $date. If you really want to report this, use
283 "perlbug -okay" or "perlbug -nokay".
287 # force these options
289 $::opt_S = 1; # don't prompt for send
290 $::opt_b = 1; # we have a body
291 $body = "Perl reported to build OK on this system.\n";
293 $::opt_C = 1; # don't send a copy to the local admin
294 $::opt_s = 1; # we have a subject line
295 $subject = ($::opt_n ? 'Not ' : '')
296 . "OK: perl $perl_version ${patch_tags}on"
297 ." $::Config{'archname'} $::Config{'osvers'} $subject";
305 # Possible administrator addresses, in order of confidence
306 # (Note that cf_email is not mentioned to metaconfig, since
307 # we don't really want it. We'll just take it if we have to.)
309 # This has to be after the $ok stuff above because of the way
310 # that $::opt_C is forced.
311 $cc = $::opt_C ? "" : (
312 $::opt_c || $::Config{'perladmin'}
313 || $::Config{'cf_email'} || $::Config{'cf_by'}
317 $me = $Is_MSWin32 ? $ENV{'USERNAME'}
318 : $^O eq 'os2' ? $ENV{'USER'} || $ENV{'LOGNAME'}
319 : $Is_MacOS ? $ENV{'USER'}
320 : eval { getpwuid($<) }; # May be missing
322 $from = $::Config{'cf_email'}
323 if !$from && $::Config{'cf_email'} && $::Config{'cf_by'} && $me &&
324 ($me eq $::Config{'cf_by'});
328 # Explain what perlbug is
331 This program provides an easy way to create a message reporting a bug
332 in perl, and e-mail it to $address. It is *NOT* intended for
333 sending test messages or simply verifying that perl works, *NOR* is it
334 intended for reporting bugs in third-party perl modules. It is *ONLY*
335 a means of reporting verifiable problems with the core perl distribution,
336 and any solutions to such problems, to the people who maintain perl.
338 If you're just looking for help with perl, try posting to the Usenet
339 newsgroup comp.lang.perl.misc. If you're looking for help with using
340 perl with CGI, try posting to comp.infosystems.www.programming.cgi.
344 # Prompt for subject of message, if needed
347 First of all, please provide a subject for the
348 message. It should be a concise description of
349 the bug or problem. "perl bug" or "perl problem"
350 is not a concise description.
356 while ($subject !~ /\S/) {
357 print "\nPlease enter a subject: ";
366 # Prompt for return address, if needed
368 # Try and guess return address
371 $guess = $ENV{'REPLY-TO'} || $ENV{'REPLYTO'} || '';
373 require Mac::InternetConfig;
374 $guess = $Mac::InternetConfig::InternetConfig{
375 Mac::InternetConfig::kICEmail()
382 $domain = Mail::Util::maildomain();
383 } elsif ($Is_MSWin32) {
384 $domain = $ENV{'USERDOMAIN'};
386 require Sys::Hostname;
387 $domain = Sys::Hostname::hostname();
390 if ($Is_VMS && !$::Config{'d_socket'}) {
391 $guess = "$domain\:\:$me";
393 $guess = "$me\@$domain" if $domain;
401 Your e-mail address will be useful if you need to be contacted. If the
402 default shown is not your full internet e-mail address, please correct it.
407 So that you may be contacted if necessary, please enter
408 your full internet e-mail address here.
417 print "Your address [$guess]: ";
420 $from = $guess if $from eq '';
424 if ($from eq $cc or $me eq $cc) {
425 # Try not to copy ourselves
429 # Prompt for administrator address, unless an override was given
430 if( !$::opt_C and !$::opt_c ) {
432 A copy of this report can be sent to your local
433 perl administrator. If the address is wrong, please
434 correct it, or enter 'none' or 'yourself' to not send
437 print "Local perl administrator [$cc]: ";
438 my $entry = scalar <>;
443 $cc = '' if $me eq $cc;
447 $cc = '' if $cc =~ /^(none|yourself|me|myself|ourselves)$/i;
448 $andcc = " and $cc" if $cc;
450 # Prompt for editor, if no override is given
452 unless ($::opt_e || $::opt_f || $::opt_b) {
454 Now you need to supply the bug report. Try to make
455 the report concise but descriptive. Include any
456 relevant detail. If you are reporting something
457 that does not work as you think it should, please
458 try to include example of both the actual
459 result, and what you expected.
461 Some information about your local
462 perl configuration will automatically be included
463 at the end of the report. If you are using any
464 unusual version of perl, please try and confirm
465 exactly which versions are relevant.
467 You will probably want to use an editor to enter
468 the report. If "$ed" is the editor you want
469 to use, then just press Enter, otherwise type in
470 the name of the editor you would like to use.
472 If you would like to use a prepared file, type
473 "file", and you will be asked for the filename.
475 print "Editor [$ed]: ";
476 my $entry =scalar <>;
480 if ($entry eq "file") {
482 } elsif ($entry ne "") {
487 # Prompt for category of bug
488 $category ||= ask_for_alternatives('category');
490 # Prompt for severity of bug
491 $severity ||= ask_for_alternatives('severity');
493 # Generate scratch file to edit report in
494 $filename = filename();
496 # Prompt for file to read report from, if needed
497 if ($usefile and !$file) {
500 What is the name of the file that contains your report?
503 my $entry = scalar <>;
508 No filename? I'll let you go back and choose an editor again.
513 unless (-f $entry and -r $entry) {
515 I'm sorry, but I can't read from `$entry'. Maybe you mistyped the name of
516 the file? If you don't want to send a file, just enter a blank line and you
517 can get back to the editor selection.
525 open(REP,">$filename") or die "Unable to create report file `$filename': $!\n";
526 my $reptype = !$ok ? "bug" : $::opt_n ? "build failure" : "success";
529 This is a $reptype report for perl from $from,
530 generated with the help of perlbug $Version running under perl $perl_version.
538 or die "Unable to read report file from `$file': $!\n";
542 close(F) or die "Error closing `$file': $!";
546 -----------------------------------------------------------------
547 [Please enter your report here]
551 [Please do not change anything below this line]
552 -----------------------------------------------------------------
556 close(REP) or die "Error closing report file: $!";
558 # read in the report template once so that
559 # we can track whether the user does any editing.
560 # yes, *all* whitespace is ignored.
561 open(REP, "<$filename") or die "Unable to open report file `$filename': $!\n";
566 close(REP) or die "Error closing report file `$filename': $!";
586 print OUT "This perlbug was built using Perl $config_tag1\n",
587 "It is being executed now by Perl $config_tag2.\n\n"
588 if $config_tag2 ne $config_tag1;
591 Site configuration information for perl $perl_version:
594 if ($::Config{cf_by} and $::Config{cf_time}) {
595 print OUT "Configured by $::Config{cf_by} at $::Config{cf_time}.\n\n";
597 print OUT Config::myconfig;
600 print OUT join "\n ", "Locally applied patches:", @patches;
607 \@INC for perl $perl_version:
616 Environment for perl $perl_version:
619 qw(PATH LD_LIBRARY_PATH LANG PERL_BADLANG SHELL HOME LOGDIR LANGUAGE);
620 push @env, $Config{ldlibpthname} if $Config{ldlibpthname} ne '';
621 push @env, grep /^(?:PERL|LC_|LANG)/, keys %ENV;
624 for my $env (sort keys %env) {
626 exists $ENV{$env} ? "=$ENV{$env}" : ' (unset)',
630 print OUT "\nComplete configuration data for perl $perl_version:\n\n";
632 foreach (sort keys %::Config) {
633 $value = $::Config{$_};
635 print OUT "$_='$value'\n";
642 if ($usefile || $body) {
644 Please make sure that the name of the editor you want to use is correct.
646 print "Editor [$ed]: ";
647 my $entry =scalar <>;
649 $ed = $entry unless $entry eq '';
654 $sts = system("$ed $filename") unless $Is_MacOS;
656 require ExtUtils::MakeMaker;
657 ExtUtils::MM_MacOS::launch_file($filename);
659 Press Enter when done.
665 The editor you chose (`$ed') could apparently not be run!
666 Did you mistype the name of your editor? If so, please
667 correct it here, otherwise just press Enter.
669 print "Editor [$ed]: ";
670 my $entry =scalar <>;
678 You may want to save your report to a file, so you can edit and mail it
684 return if ($ok and not $::opt_n) || $body;
685 # Check that we have a report that has some, eh, report in it.
688 open(REP, "<$filename") or die "Couldn't open `$filename': $!\n";
689 # a strange way to check whether any significant editing
690 # have been done: check whether any new non-empty lines
691 # have been added. Yes, the below code ignores *any* space
695 $unseen++ if $_ ne '' and not exists $REP{$_};
698 while ($unseen == 0) {
700 I am sorry but it looks like you did not report anything.
702 print "Action (Retry Edit/Cancel) ";
703 my ($action) = scalar(<>);
704 if ($action =~ /^[re]/i) { # <R>etry <E>dit
706 } elsif ($action =~ /^[cq]/i) { # <C>ancel, <Q>uit
713 1 while unlink($filename); # remove all versions under VMS
714 print "\nCancelling.\n";
719 # Report is done, prompt for further action
723 Now that you have completed your report, would you like to send
724 the message to $address$andcc, display the message on
725 the screen, re-edit it, or cancel without sending anything?
726 You may also save the message as a file to mail at another time.
729 print "Action (Send/Display/Edit/Cancel/Save to File): ";
730 my $action = scalar <>;
733 if ($action =~ /^(f|sa)/i) { # <F>ile/<Sa>ve
734 my $file_save = $outfile || "perlbug.rep";
735 print "\n\nName of file to save message in [$file_save]: ";
736 my $file = scalar <>;
738 $file = $file_save if $file eq "";
740 unless (open(FILE, ">$file")) {
741 print "\nError opening $file: $!\n\n";
744 open(REP, "<$filename") or die "Couldn't open file `$filename': $!\n";
745 print FILE "To: $address\nSubject: $subject\n";
746 print FILE "Cc: $cc\n" if $cc;
747 print FILE "Reply-To: $from\n" if $from;
749 while (<REP>) { print FILE }
750 close(REP) or die "Error closing report file `$filename': $!";
751 close(FILE) or die "Error closing $file: $!";
753 print "\nMessage saved in `$file'.\n";
755 } elsif ($action =~ /^(d|l|sh)/i ) { # <D>isplay, <L>ist, <Sh>ow
756 # Display the message
757 open(REP, "<$filename") or die "Couldn't open file `$filename': $!\n";
758 while (<REP>) { print $_ }
759 close(REP) or die "Error closing report file `$filename': $!";
760 } elsif ($action =~ /^se/i) { # <S>end
762 print "Are you certain you want to send this message?\n"
763 . 'Please type "yes" if you are: ';
764 my $reply = scalar <STDIN>;
766 if ($reply eq "yes") {
770 That wasn't a clear "yes", so I won't send your message. If you are sure
771 your message should be sent, type in "yes" (without the quotes) at the
775 } elsif ($action =~ /^[er]/i) { # <E>dit, <R>e-edit
778 } elsif ($action =~ /^[qc]/i) { # <C>ancel, <Q>uit
780 } elsif ($action =~ /^s/i) {
782 I'm sorry, but I didn't understand that. Please type "send" or "save".
790 # Message has been accepted for transmission -- Send the message
792 open SENDMAIL, ">$outfile" or die "Couldn't open '$outfile': $!\n";
796 $msg = new Mail::Send Subject => $subject, To => $address;
797 $msg->cc($cc) if $cc;
798 $msg->add("Reply-To",$from) if $from;
801 open(REP, "<$filename") or die "Couldn't open `$filename': $!\n";
802 while (<REP>) { print $fh $_ }
803 close(REP) or die "Error closing $filename: $!";
806 print "\nMessage sent.\n";
808 if ( ($address =~ /@/ and $address !~ /^\w+%"/) or
809 ($cc =~ /@/ and $cc !~ /^\w+%"/) ) {
811 foreach (qw[ IN MX SMTP UCX PONY WINS ], '') {
812 $prefix = "$_%", last if $ENV{"MAIL\$PROTOCOL_$_"};
814 $address = qq[${prefix}"$address"] unless $address =~ /^\w+%"/;
815 $cc = qq[${prefix}"$cc"] unless !$cc || $cc =~ /^\w+%"/;
817 $subject =~ s/"/""/g; $address =~ s/"/""/g; $cc =~ s/"/""/g;
818 my $sts = system(qq[mail/Subject="$subject" $filename. "$address","$cc"]);
822 (leaving bug report in $filename): $sts
827 for (qw(/usr/lib/sendmail /usr/sbin/sendmail /usr/ucblib/sendmail)) {
828 $sendmail = $_, last if -e $_;
830 if ($^O eq 'os2' and $sendmail eq "") {
831 my $path = $ENV{PATH};
833 my @path = split /$Config{'path_sep'}/, $path;
835 $sendmail = "$_/sendmail", last if -e "$_/sendmail";
836 $sendmail = "$_/sendmail.exe", last if -e "$_/sendmail.exe";
840 paraprint(<<"EOF"), die "\n" if $sendmail eq "";
841 I am terribly sorry, but I cannot find sendmail, or a close equivalent, and
842 the perl package Mail::Send has not been installed, so I can't send your bug
843 report. We apologize for the inconvenience.
845 So you may attempt to find some way of sending your message, it has
846 been left in the file `$filename'.
848 open(SENDMAIL, "|$sendmail -t -oi") || die "'|$sendmail -t -oi' failed: $!";
850 print SENDMAIL "To: $address\n";
851 print SENDMAIL "Subject: $subject\n";
852 print SENDMAIL "Cc: $cc\n" if $cc;
853 print SENDMAIL "Reply-To: $from\n" if $from;
854 print SENDMAIL "\n\n";
855 open(REP, "<$filename") or die "Couldn't open `$filename': $!\n";
856 while (<REP>) { print SENDMAIL $_ }
857 close(REP) or die "Error closing $filename: $!";
859 if (close(SENDMAIL)) {
860 printf "\nMessage %s.\n", $outfile ? "saved" : "sent";
862 warn "\nSendmail returned status '", $? >> 8, "'\n";
865 1 while unlink($filename); # remove all versions under VMS
871 A program to help generate bug reports about perl5, and mail them.
872 It is designed to be used interactively. Normally no arguments will
876 $0 [-v] [-a address] [-s subject] [-b body | -f inpufile ] [ -F outputfile ]
877 [-r returnaddress] [-e editor] [-c adminaddress | -C] [-S] [-t] [-h]
878 $0 [-v] [-r returnaddress] [-A] [-ok | -okay | -nok | -nokay]
880 Simplest usage: run "$0", and follow the prompts.
884 -v Include Verbose configuration data in the report
885 -f File containing the body of the report. Use this to
886 quickly send a prepared message.
887 -F File to output the resulting mail message to, instead of mailing.
888 -S Send without asking for confirmation.
889 -a Address to send the report to. Defaults to `$address'.
890 -c Address to send copy of report to. Defaults to `$cc'.
891 -C Don't send copy to administrator.
892 -s Subject to include with the message. You will be prompted
893 if you don't supply one on the command line.
894 -b Body of the report. If not included on the command line, or
895 in a file with -f, you will get a chance to edit the message.
896 -r Your return address. The program will ask you to confirm
897 this if you don't give it here.
899 -t Test mode. The target address defaults to `$testaddress'.
900 -d Data mode. This prints out your configuration data, without mailing
901 anything. You can use this with -v to get more complete data.
902 -A Don't send a bug received acknowledgement to the return address.
903 -ok Report successful build on this system to perl porters
904 (use alone or with -v). Only use -ok if *everything* was ok:
905 if there were *any* problems at all, use -nok.
906 -okay As -ok but allow report from old builds.
907 -nok Report unsuccessful build on this system to perl porters
908 (use alone or with -v). You must describe what went wrong
909 in the body of the report which you will be asked to edit.
910 -nokay As -nok but allow report from old builds.
911 -h Print this help message.
917 my $dir = File::Spec->tmpdir();
918 $filename = "bugrep0$$";
919 $filename++ while -e File::Spec->catfile($dir, $filename);
920 $filename = File::Spec->catfile($dir, $filename);
924 my @paragraphs = split /\n{2,}/, "@_";
926 for (@paragraphs) { # implicit local $_
934 ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ~~
942 perlbug - how to submit bug reports on Perl
946 B<perlbug> S<[ B<-v> ]> S<[ B<-a> I<address> ]> S<[ B<-s> I<subject> ]>
947 S<[ B<-b> I<body> | B<-f> I<inputfile> ]> S<[ B<-F> I<outputfile> ]>
948 S<[ B<-r> I<returnaddress> ]>
949 S<[ B<-e> I<editor> ]> S<[ B<-c> I<adminaddress> | B<-C> ]>
950 S<[ B<-S> ]> S<[ B<-t> ]> S<[ B<-d> ]> S<[ B<-A> ]> S<[ B<-h> ]>
952 B<perlbug> S<[ B<-v> ]> S<[ B<-r> I<returnaddress> ]>
953 S<[ B<-A> ]> S<[ B<-ok> | B<-okay> | B<-nok> | B<-nokay> ]>
957 A program to help generate bug reports about perl or the modules that
958 come with it, and mail them.
960 If you have found a bug with a non-standard port (one that was not part
961 of the I<standard distribution>), a binary distribution, or a
962 non-standard module (such as Tk, CGI, etc), then please see the
963 documentation that came with that distribution to determine the correct
964 place to report bugs.
966 C<perlbug> is designed to be used interactively. Normally no arguments
967 will be needed. Simply run it, and follow the prompts.
969 If you are unable to run B<perlbug> (most likely because you don't have
970 a working setup to send mail that perlbug recognizes), you may have to
971 compose your own report, and email it to B<perlbug@perl.org>. You might
972 find the B<-d> option useful to get summary information in that case.
974 In any case, when reporting a bug, please make sure you have run through
979 =item What version of Perl you are running?
981 Type C<perl -v> at the command line to find out.
983 =item Are you running the latest released version of perl?
985 Look at http://www.perl.com/ to find out. If it is not the latest
986 released version, get that one and see whether your bug has been
987 fixed. Note that bug reports about old versions of Perl, especially
988 those prior to the 5.0 release, are likely to fall upon deaf ears.
989 You are on your own if you continue to use perl1 .. perl4.
991 =item Are you sure what you have is a bug?
993 A significant number of the bug reports we get turn out to be documented
994 features in Perl. Make sure the behavior you are witnessing doesn't fall
995 under that category, by glancing through the documentation that comes
996 with Perl (we'll admit this is no mean task, given the sheer volume of
997 it all, but at least have a look at the sections that I<seem> relevant).
999 Be aware of the familiar traps that perl programmers of various hues
1000 fall into. See L<perltrap>.
1002 Check in L<perldiag> to see what any Perl error message(s) mean.
1003 If message isn't in perldiag, it probably isn't generated by Perl.
1004 Consult your operating system documentation instead.
1006 If you are on a non-UNIX platform check also L<perlport>, as some
1007 features may be unimplemented or work differently.
1009 Try to study the problem under the Perl debugger, if necessary.
1012 =item Do you have a proper test case?
1014 The easier it is to reproduce your bug, the more likely it will be
1015 fixed, because if no one can duplicate the problem, no one can fix it.
1016 A good test case has most of these attributes: fewest possible number
1017 of lines; few dependencies on external commands, modules, or
1018 libraries; runs on most platforms unimpeded; and is self-documenting.
1020 A good test case is almost always a good candidate to be on the perl
1021 test suite. If you have the time, consider making your test case so
1022 that it will readily fit into the standard test suite.
1024 Remember also to include the B<exact> error messages, if any.
1025 "Perl complained something" is not an exact error message.
1027 If you get a core dump (or equivalent), you may use a debugger
1028 (B<dbx>, B<gdb>, etc) to produce a stack trace to include in the bug
1029 report. NOTE: unless your Perl has been compiled with debug info
1030 (often B<-g>), the stack trace is likely to be somewhat hard to use
1031 because it will most probably contain only the function names and not
1032 their arguments. If possible, recompile your Perl with debug info and
1033 reproduce the dump and the stack trace.
1035 =item Can you describe the bug in plain English?
1037 The easier it is to understand a reproducible bug, the more likely it
1038 will be fixed. Anything you can provide by way of insight into the
1039 problem helps a great deal. In other words, try to analyze the
1040 problem (to the extent you can) and report your discoveries.
1042 =item Can you fix the bug yourself?
1044 A bug report which I<includes a patch to fix it> will almost
1045 definitely be fixed. Use the C<diff> program to generate your patches
1046 (C<diff> is being maintained by the GNU folks as part of the B<diffutils>
1047 package, so you should be able to get it from any of the GNU software
1048 repositories). If you do submit a patch, the cool-dude counter at
1049 perlbug@perl.org will register you as a savior of the world. Your
1050 patch may be returned with requests for changes, or requests for more
1051 detailed explanations about your fix.
1053 Here are some clues for creating quality patches: Use the B<-c> or
1054 B<-u> switches to the diff program (to create a so-called context or
1055 unified diff). Make sure the patch is not reversed (the first
1056 argument to diff is typically the original file, the second argument
1057 your changed file). Make sure you test your patch by applying it with
1058 the C<patch> program before you send it on its way. Try to follow the
1059 same style as the code you are trying to patch. Make sure your patch
1060 really does work (C<make test>, if the thing you're patching supports
1063 =item Can you use C<perlbug> to submit the report?
1065 B<perlbug> will, amongst other things, ensure your report includes
1066 crucial information about your version of perl. If C<perlbug> is unable
1067 to mail your report after you have typed it in, you may have to compose
1068 the message yourself, add the output produced by C<perlbug -d> and email
1069 it to B<perlbug@perl.org>. If, for some reason, you cannot run
1070 C<perlbug> at all on your system, be sure to include the entire output
1071 produced by running C<perl -V> (note the uppercase V).
1073 Whether you use C<perlbug> or send the email manually, please make
1074 your Subject line informative. "a bug" not informative. Neither is
1075 "perl crashes" nor "HELP!!!". These don't help.
1076 A compact description of what's wrong is fine.
1080 Having done your bit, please be prepared to wait, to be told the bug
1081 is in your code, or even to get no reply at all. The Perl maintainers
1082 are busy folks, so if your problem is a small one or if it is difficult
1083 to understand or already known, they may not respond with a personal reply.
1084 If it is important to you that your bug be fixed, do monitor the
1085 C<Changes> file in any development releases since the time you submitted
1086 the bug, and encourage the maintainers with kind words (but never any
1087 flames!). Feel free to resend your bug report if the next released
1088 version of perl comes out and your bug is still present.
1096 Address to send the report to. Defaults to `perlbug@perl.org'.
1100 Don't send a bug received acknowledgement to the reply address.
1101 Generally it is only a sensible to use this option if you are a
1102 perl maintainer actively watching perl porters for your message to
1107 Body of the report. If not included on the command line, or
1108 in a file with B<-f>, you will get a chance to edit the message.
1112 Don't send copy to administrator.
1116 Address to send copy of report to. Defaults to the address of the
1117 local perl administrator (recorded when perl was built).
1121 Data mode (the default if you redirect or pipe output). This prints out
1122 your configuration data, without mailing anything. You can use this
1123 with B<-v> to get more complete data.
1131 File containing the body of the report. Use this to quickly send a
1136 File to output the results to instead of sending as an email. Useful
1137 particularly when running perlbug on a machine with no direct internet
1142 Prints a brief summary of the options.
1146 Report successful build on this system to perl porters. Forces B<-S>
1147 and B<-C>. Forces and supplies values for B<-s> and B<-b>. Only
1148 prompts for a return address if it cannot guess it (for use with
1149 B<make>). Honors return address specified with B<-r>. You can use this
1150 with B<-v> to get more complete data. Only makes a report if this
1151 system is less than 60 days old.
1155 As B<-ok> except it will report on older systems.
1159 Report unsuccessful build on this system. Forces B<-C>. Forces and
1160 supplies a value for B<-s>, then requires you to edit the report
1161 and say what went wrong. Alternatively, a prepared report may be
1162 supplied using B<-f>. Only prompts for a return address if it
1163 cannot guess it (for use with B<make>). Honors return address
1164 specified with B<-r>. You can use this with B<-v> to get more
1165 complete data. Only makes a report if this system is less than 60
1170 As B<-nok> except it will report on older systems.
1174 Your return address. The program will ask you to confirm its default
1175 if you don't use this option.
1179 Send without asking for confirmation.
1183 Subject to include with the message. You will be prompted if you don't
1184 supply one on the command line.
1188 Test mode. The target address defaults to `perlbug-test@perl.com'.
1192 Include verbose configuration data in the report.
1198 Kenneth Albanowski (E<lt>kjahds@kjahds.comE<gt>), subsequently I<doc>tored
1199 by Gurusamy Sarathy (E<lt>gsar@activestate.comE<gt>), Tom Christiansen
1200 (E<lt>tchrist@perl.comE<gt>), Nathan Torkington (E<lt>gnat@frii.comE<gt>),
1201 Charles F. Randall (E<lt>cfr@pobox.comE<gt>), Mike Guy
1202 (E<lt>mjtg@cam.a.ukE<gt>), Dominic Dunlop (E<lt>domo@computer.orgE<gt>),
1203 Hugo van der Sanden (E<lt>hv@crypt0.demon.co.ukE<gt>),
1204 Jarkko Hietaniemi (E<lt>jhi@iki.fiE<gt>), Chris Nandor
1205 (E<lt>pudge@pobox.comE<gt>), Jon Orwant (E<lt>orwant@media.mit.eduE<gt>,
1206 and Richard Foley (E<lt>richard@rfi.netE<gt>).
1210 perl(1), perldebug(1), perldiag(1), perlport(1), perltrap(1),
1211 diff(1), patch(1), dbx(1), gdb(1)
1215 None known (guess what must have been used to report them?)
1221 close OUT or die "Can't close $file: $!";
1222 chmod 0755, $file or die "Can't reset permissions for $file: $!\n";
1223 exec("$Config{'eunicefix'} $file") if $Config{'eunicefix'} ne ':';