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 # get patchlevel.h timestamp
27 -e catfile(updir, "patchlevel.h")
28 or die "Can't find patchlevel.h: $!";
30 my $patchlevel_date = (stat _)[9];
32 # TO DO (perhaps): store/embed $Config::config_sh into perlbug. When perlbug is
33 # used, compare $Config::config_sh with the stored version. If they differ then
34 # append a list of individual differences to the bug report.
37 print "Extracting $file (with variable substitutions)\n";
39 # In this section, perl variables will be expanded during extraction.
40 # You can use $Config{...} to use Configure variables.
42 my $extract_version = sprintf("%vd", $^V);
44 print OUT <<"!GROK!THIS!";
46 eval 'exec $Config{perlpath} -S \$0 \${1+"\$@"}'
47 if \$running_under_some_shell;
49 my \$config_tag1 = '$extract_version - $Config{cf_time}';
51 my \$patchlevel_date = $patchlevel_date;
54 # In the following, perl variables are not expanded during extraction.
56 print OUT <<'!NO!SUBS!';
57 my @patches = Config::local_patches();
58 my $patch_tags = join "", map /(\S+)/ ? "+$1 " : (), @patches;
60 BEGIN { pop @INC if $INC[-1] eq '.' }
64 use File::Spec; # keep perlbug Perl 5.005 compatible
66 use File::Basename 'basename';
71 eval { require Mail::Send;};
72 $::HaveSend = ($@ eq "");
73 eval { require Mail::Util; } ;
74 $::HaveUtil = ($@ eq "");
75 # use secure tempfiles wherever possible
76 eval { require File::Temp; };
77 $::HaveTemp = ($@ eq "");
78 eval { require Module::CoreList; };
79 $::HaveCoreList = ($@ eq "");
80 eval { require Text::Wrap; };
81 $::HaveWrap = ($@ eq "");
87 # make sure failure (transmission-wise) of Mail::Send is accounted for.
88 # (This may work now. Unsure of the original author's issue -JESSE 2008-06-08)
91 my( $file, $usefile, $cc, $address, $bugaddress, $testaddress, $thanksaddress,
92 $filename, $messageid, $domain, $subject, $from, $verbose, $ed, $outfile,
93 $fh, $me, $body, $andcc, %REP, $ok, $thanks, $progname,
94 $Is_MSWin32, $Is_Linux, $Is_VMS, $Is_OpenBSD,
95 $report_about_module, $category, $severity,
96 %opt, $have_attachment, $attachments, $has_patch, $mime_boundary
99 my $running_noninteractively = !-t STDIN;
101 my $perl_version = $^V ? sprintf("%vd", $^V) : $];
103 my $config_tag2 = "$perl_version - $Config{cf_time}";
107 if ($opt{h}) { Help(); exit; }
108 if ($opt{d}) { Dump(*STDOUT); exit; }
109 if ($running_noninteractively && !$opt{t} && !($ok and not $opt{n})) {
111 Please use $progname interactively. If you want to
112 include a file, you can use the -f switch.
118 Edit() unless $usefile || ($ok and not $opt{n});
121 save_message_to_disk($outfile);
125 print "\nThank you for taking the time to send a thank-you message!\n\n";
128 Please note that mailing lists are moderated, your message may take a while to
132 print "\nThank you for taking the time to file a bug report!\n\n";
135 Please note that mailing lists are moderated, your message may take a while to
136 show up. If you do not receive an automated response acknowledging your message
137 within a few hours (check your SPAM folder and outgoing mail) please consider
138 sending an email directly from your mail client to perlbug\@perl.org.
146 sub ask_for_alternatives { # (category|severity)
152 # Inevitably some of these will end up in RT whatever we do:
153 'thanks' => 'thanks',
154 'opts' => [qw(core docs install library utilities)], # patch, notabug
160 'opts' => [qw(critical high medium low wishlist none)], # zero
163 die "Invalid alternative ($name) requested\n" unless grep(/^$name$/, keys %alts);
165 my $what = $ok || $thanks;
167 $alt = $alts{$name}{$what};
169 my @alts = @{$alts{$name}{'opts'}};
172 Please pick a $name from the following list:
179 die "Invalid $name: aborting.\n";
181 $alt = _prompt('', "\u$name", $alts{$name}{'default'});
182 $alt ||= $alts{$name}{'default'};
183 } while !((($alt) = grep(/^$alt/i, @alts)));
189 # -------- Setup --------
191 $Is_MSWin32 = $^O eq 'MSWin32';
192 $Is_VMS = $^O eq 'VMS';
193 $Is_Linux = lc($^O) eq 'linux';
194 $Is_OpenBSD = lc($^O) eq 'openbsd';
196 if (!getopts("Adhva:s:b:f:F:r:e:SCc:to:n:T:p:", \%opt)) { Help(); exit; };
198 # This comment is needed to notify metaconfig that we are
199 # using the $perladmin, $cf_by, and $cf_time definitions.
201 # -------- Configuration ---------
204 $bugaddress = 'perlbug@perl.org';
207 $testaddress = 'perlbug-test@perl.org';
210 $thanksaddress = 'perl-thanks@perl.org';
212 if (basename ($0) =~ /^perlthanks/i) {
213 # invoked as perlthanks
215 $opt{C} = 1; # don't send a copy to the local admin
222 $progname = $thanks ? 'perlthanks' : 'perlbug';
224 $address = $opt{a} || ($opt{t} ? $testaddress
225 : $thanks ? $thanksaddress : $bugaddress);
227 # Users address, used in message and in From and Reply-To headers
228 $from = $opt{r} || "";
230 # Include verbose configuration information
231 $verbose = $opt{v} || 0;
233 # Subject of bug-report message
234 $subject = $opt{s} || "";
237 $usefile = ($opt{f} || 0);
239 # File to send as report
240 $file = $opt{f} || "";
242 # We have one or more attachments
243 $have_attachment = ($opt{p} || 0);
244 $mime_boundary = ('-' x 12) . "$Version.perlbug" if $have_attachment;
246 # Comma-separated list of attachments
247 $attachments = $opt{p} || "";
248 $has_patch = 0; # TBD based on file type
250 for my $attachment (split /\s*,\s*/, $attachments) {
251 unless (-f $attachment && -r $attachment) {
252 die "The attachment $attachment is not a readable file: $!\n";
254 $has_patch = 1 if $attachment =~ m/\.(patch|diff)$/;
258 $outfile = $opt{F} || "";
261 $body = $opt{b} || "";
264 $ed = $opt{e} || $ENV{VISUAL} || $ENV{EDITOR} || $ENV{EDIT}
265 || ($Is_VMS && "edit/tpu")
266 || ($Is_MSWin32 && "notepad")
269 # Not OK - provide build failure template by finessing OK report
271 if (substr($opt{n}, 0, 2) eq 'ok' ) {
272 $opt{o} = substr($opt{n}, 1);
279 # OK - send "OK" report for build on this system
282 if ($opt{o} eq 'k' or $opt{o} eq 'kay') {
283 my $age = time - $patchlevel_date;
284 if ($opt{o} eq 'k' and $age > 60 * 24 * 60 * 60 ) {
285 my $date = localtime $patchlevel_date;
287 "perlbug -ok" and "perlbug -nok" do not report on Perl versions which
288 are more than 60 days old. This Perl version was constructed on
289 $date. If you really want to report this, use
290 "perlbug -okay" or "perlbug -nokay".
294 # force these options
296 $opt{S} = 1; # don't prompt for send
297 $opt{b} = 1; # we have a body
298 $body = "Perl reported to build OK on this system.\n";
300 $opt{C} = 1; # don't send a copy to the local admin
301 $opt{s} = 1; # we have a subject line
302 $subject = ($opt{n} ? 'Not ' : '')
303 . "OK: perl $perl_version ${patch_tags}on"
304 ." $::Config{'archname'} $::Config{'osvers'} $subject";
312 # Possible administrator addresses, in order of confidence
313 # (Note that cf_email is not mentioned to metaconfig, since
314 # we don't really want it. We'll just take it if we have to.)
316 # This has to be after the $ok stuff above because of the way
317 # that $opt{C} is forced.
318 $cc = $opt{C} ? "" : (
319 $opt{c} || $::Config{'perladmin'}
320 || $::Config{'cf_email'} || $::Config{'cf_by'}
324 $domain = Mail::Util::maildomain();
325 } elsif ($Is_MSWin32) {
326 $domain = $ENV{'USERDOMAIN'};
328 require Sys::Hostname;
329 $domain = Sys::Hostname::hostname();
333 $messageid = "<$::Config{'version'}_${$}_".time."\@$domain>";
336 $me = $Is_MSWin32 ? $ENV{'USERNAME'}
337 : $^O eq 'os2' ? $ENV{'USER'} || $ENV{'LOGNAME'}
338 : eval { getpwuid($<) }; # May be missing
340 $from = $::Config{'cf_email'}
341 if !$from && $::Config{'cf_email'} && $::Config{'cf_by'} && $me &&
342 ($me eq $::Config{'cf_by'});
346 # Explain what perlbug is
350 This program provides an easy way to send a thank-you message back to the
351 authors and maintainers of perl.
353 If you wish to submit a bug report, please run it without the -T flag
354 (or run the program perlbug rather than perlthanks)
358 This program provides an easy way to create a message reporting a
359 bug in the core perl distribution (along with tests or patches)
360 to the volunteers who maintain perl at $address. To send a thank-you
361 note to $thanksaddress instead of a bug report, please run 'perlthanks'.
363 Please do not use $0 to send test messages, test whether perl
364 works, or to report bugs in perl modules from CPAN.
366 Suggestions for how to find help using Perl can be found at
367 http://perldoc.perl.org/perlcommunity.html
372 # Prompt for subject of message, if needed
374 if ($subject && TrivialSubject($subject)) {
380 "First of all, please provide a subject for the message.\n";
383 This should be a concise description of your bug or problem
384 which will help the volunteers working to improve perl to categorize
385 and resolve the issue. Be as specific and descriptive as
386 you can. A subject like "perl bug" or "perl problem" will make it
387 much less likely that your issue gets the attention it deserves.
393 $subject = _prompt('','Subject');
396 $subject = 'Thanks for Perl';
401 } while (TrivialSubject($subject));
403 $subject = '[PATCH] ' . $subject
404 if $has_patch && ($subject !~ m/^\[PATCH/i);
406 # Prompt for return address, if needed
408 # Try and guess return address
411 $guess = $ENV{'REPLY-TO'} || $ENV{'REPLYTO'} || $ENV{'EMAIL'}
415 # move $domain to where we can use it elsewhere
417 if ($Is_VMS && !$::Config{'d_socket'}) {
418 $guess = "$domain\:\:$me";
420 $guess = "$me\@$domain" if $domain;
428 Perl's developers may need your email address to contact you for
429 further information about your issue or to inform you when it is
430 resolved. If the default shown is not your email address, please
436 Please enter your full internet email address so that Perl's
437 developers can contact you with questions about your issue or to
438 inform you that it has been resolved.
447 $from = _prompt('','Your address',$guess);
448 $from = $guess if $from eq '';
452 if ($from eq $cc or $me eq $cc) {
453 # Try not to copy ourselves
457 # Prompt for administrator address, unless an override was given
458 if( !$opt{C} and !$opt{c} ) {
459 my $description = <<EOF;
460 $0 can send a copy of this report to your local perl
461 administrator. If the address below is wrong, please correct it,
462 or enter 'none' or 'yourself' to not send a copy.
464 my $entry = _prompt($description, "Local perl administrator", $cc);
468 $cc = '' if $me eq $cc;
472 $cc = '' if $cc =~ /^(none|yourself|me|myself|ourselves)$/i;
479 # Prompt for editor, if no override is given
481 unless ($opt{e} || $opt{f} || $opt{b}) {
485 chomp (my $common_end = <<"EOF");
486 You will probably want to use a text editor to enter the body of
487 your report. If "$ed" is the editor you want to use, then just press
488 Enter, otherwise type in the name of the editor you would like to
491 If you have already composed the body of your report, you may enter
492 "file", and $0 will prompt you to enter the name of the file
493 containing your report.
497 $description = <<"EOF";
498 It's now time to compose your thank-you message.
500 Some information about your local perl configuration will automatically
501 be included at the end of your message, because we're curious about
502 the different ways that people build and use perl. If you'd rather
503 not share this information, you're welcome to delete it.
508 $description = <<"EOF";
509 It's now time to compose your bug report. Try to make the report
510 concise but descriptive. Please include any detail which you think
511 might be relevant or might help the volunteers working to improve
512 perl. If you are reporting something that does not work as you think
513 it should, please try to include examples of the actual result and of
516 Some information about your local perl configuration will automatically
517 be included at the end of your report. If you are using an unusual
518 version of perl, it would be useful if you could confirm that you
519 can replicate the problem on a standard build of perl as well.
525 my $entry = _prompt($description, "Editor", $ed);
527 if ($entry eq "file") {
529 } elsif ($entry ne "") {
533 if ($::HaveCoreList && !$ok && !$thanks) {
534 my $description = <<EOF;
535 If your bug is about a Perl module rather than a core language
536 feature, please enter its name here. If it's not, just hit Enter
537 to skip this question.
541 while ($entry eq '') {
542 $entry = _prompt($description, 'Module');
543 my $first_release = Module::CoreList->first_release($entry);
544 if ($entry and not $first_release) {
546 $entry is not a "core" Perl module. Please check that you entered
547 its name correctly. If it is correct, quit this program, try searching
548 for $entry on http://rt.cpan.org, and report your issue there.
552 } elsif (my $bug_tracker = $Module::CoreList::bug_tracker{$entry}) {
554 $entry included with core Perl is copied directly from the CPAN distribution.
555 Please report bugs in $entry directly to its maintainers using $bug_tracker
559 $category ||= 'library';
560 $report_about_module = $entry;
568 # Prompt for category of bug
569 $category ||= ask_for_alternatives('category');
571 # Prompt for severity of bug
572 $severity ||= ask_for_alternatives('severity');
574 # Generate scratch file to edit report in
575 $filename = filename();
577 # Prompt for file to read report from, if needed
578 if ($usefile and !$file) {
580 my $description = <<EOF;
581 What is the name of the file that contains your report?
583 my $entry = _prompt($description, "Filename");
587 It seems you didn't enter a filename. Please choose to use a text
588 editor or enter a filename.
593 unless (-f $entry and -r $entry) {
595 '$entry' doesn't seem to be a readable file. You may have mistyped
596 its name or may not have permission to read it.
598 If you don't want to use a file as the content of your report, just
599 hit Enter and you'll be able to select a text editor instead.
607 open(REP, '>:raw', $filename) or die "Unable to create report file '$filename': $!\n";
608 binmode(REP, ':raw :crlf') if $Is_MSWin32;
610 my $reptype = !$ok ? ($thanks ? 'thank-you' : 'bug')
611 : $opt{n} ? "build failure" : "success";
614 This is a $reptype report for perl from $from,
615 generated with the help of perlbug $Version running under perl $perl_version.
622 open(F, '<:raw', $file)
623 or die "Unable to read report file from '$file': $!\n";
624 binmode(F, ':raw :crlf') if $Is_MSWin32;
628 close(F) or die "Error closing '$file': $!";
633 -----------------------------------------------------------------
634 [Please enter your thank-you message here]
638 [You're welcome to delete anything below this line]
639 -----------------------------------------------------------------
644 -----------------------------------------------------------------
645 [Please describe your issue here]
649 [Please do not change anything below this line]
650 -----------------------------------------------------------------
655 close(REP) or die "Error closing report file: $!";
657 # Set up an initial report fingerprint so we can compare it later
658 _fingerprint_lines_in_report();
665 # these won't have been set if run with -d
666 $category ||= 'core';
683 if ($report_about_module ) {
685 module=$report_about_module
696 print OUT "This perlbug was built using Perl $config_tag1\n",
697 "It is being executed now by Perl $config_tag2.\n\n"
698 if $config_tag2 ne $config_tag1;
701 Site configuration information for perl $perl_version:
704 if ($::Config{cf_by} and $::Config{cf_time}) {
705 print OUT "Configured by $::Config{cf_by} at $::Config{cf_time}.\n\n";
707 print OUT Config::myconfig;
710 print OUT join "\n ", "Locally applied patches:", @patches;
717 \@INC for perl $perl_version:
726 Environment for perl $perl_version:
729 qw(PATH LD_LIBRARY_PATH LANG PERL_BADLANG SHELL HOME LOGDIR LANGUAGE);
730 push @env, $Config{ldlibpthname} if $Config{ldlibpthname} ne '';
731 push @env, grep /^(?:PERL|LC_|LANG|CYGWIN)/, keys %ENV;
734 for my $env (sort keys %env) {
736 exists $ENV{$env} ? "=$ENV{$env}" : ' (unset)',
740 print OUT "\nComplete configuration data for perl $perl_version:\n\n";
742 foreach (sort keys %::Config) {
743 $value = $::Config{$_};
744 $value = '' unless defined $value;
746 print OUT "$_='$value'\n";
753 if ($usefile || $body) {
754 my $description = "Please make sure that the name of the editor you want to use is correct.";
755 my $entry = _prompt($description, 'Editor', $ed);
756 $ed = $entry unless $entry eq '';
759 _edit_file($ed) unless $running_noninteractively;
765 my $report_written = 0;
767 while ( !$report_written ) {
768 my $exit_status = system("$editor $filename");
771 The editor you chose ('$editor') could not be run!
773 If you mistyped its name, please enter it now, otherwise just press Enter.
775 my $entry = _prompt( $desc, 'Editor', $editor );
776 if ( $entry ne "" ) {
781 You may want to save your report to a file, so you can edit and
787 return if ( $ok and not $opt{n} ) || $body;
789 # Check that we have a report that has some, eh, report in it.
791 unless ( _fingerprint_lines_in_report() ) {
792 my $description = <<EOF;
793 It looks like you didn't enter a report. You may [r]etry your edit
794 or [c]ancel this report.
796 my $action = _prompt( $description, "Action (Retry/Cancel) " );
797 if ( $action =~ /^[re]/i ) { # <R>etry <E>dit
799 } elsif ( $action =~ /^[cq]/i ) { # <C>ancel, <Q>uit
800 Cancel(); # cancel exits
803 # Ok. the user did what they needed to;
811 1 while unlink($filename); # remove all versions under VMS
812 print "\nQuitting without sending your message.\n";
817 # Report is done, prompt for further action
823 You have finished composing your message. At this point, you have
824 a few options. You can:
826 * [Se]nd the message to $address$andcc,
827 * [D]isplay the message on the screen,
828 * [R]e-edit the message
829 * Display or change the message's [su]bject
830 * Save the message to a [f]ile to mail at another time
831 * [Q]uit without sending a message
836 my $action = _prompt('', "Action (Send/Display/Edit/Subject/Save to File)",
839 if ($action =~ /^(f|sa)/i) { # <F>ile/<Sa>ve
840 if ( SaveMessage() ) { exit }
841 } elsif ($action =~ /^(d|l|sh)/i ) { # <D>isplay, <L>ist, <Sh>ow
842 # Display the message
843 print _read_report($filename);
844 if ($have_attachment) {
845 print "\n\n---\nAttachment(s):\n";
846 for my $att (split /\s*,\s*/, $attachments) { print " $att\n"; }
848 } elsif ($action =~ /^su/i) { # <Su>bject
849 my $reply = _prompt( "Subject: $subject", "If the above subject is fine, press Enter. Otherwise, type a replacement now\nSubject");
851 unless (TrivialSubject($reply)) {
853 print "Subject: $subject\n";
856 } elsif ($action =~ /^se/i) { # <S>end
858 my $reply = _prompt( "Are you certain you want to send this message?", 'Please type "yes" if you are','no');
859 if ($reply =~ /^yes$/) {
863 You didn't type "yes", so your message has not yet been sent.
866 } elsif ($action =~ /^[er]/i) { # <E>dit, <R>e-edit
869 } elsif ($action =~ /^[qc]/i) { # <C>ancel, <Q>uit
871 } elsif ($action =~ /^s/i) {
873 The command you entered was ambiguous. Please type "send", "save" or "subject".
883 /^(y(es)?|no?|help|perl( (bug|problem))?|bug|problem)$/i ||
884 length($subject) < 4 ||
885 ($subject !~ /\s/ && ! $opt{t})) { # non-whitespace is accepted in test mode
886 print "\nThe subject you entered wasn't very descriptive. Please try again.\n\n";
894 my $file_save = $outfile || "$progname.rep";
895 my $file = _prompt( '', "Name of file to save message in", $file_save );
896 save_message_to_disk($file) || return undef;
899 A copy of your message has been saved in '$file' for you to
900 send to '$address' with your normal mail client.
906 # Message has been accepted for transmission -- Send the message
908 # on linux certain "mail" implementations won't accept the subject
909 # as "~s subject" and thus the Subject header will be corrupted
910 # so don't use Mail::Send to be safe
912 if ( $::HaveSend && !$Is_Linux && !$Is_OpenBSD ) {
913 _send_message_mailsend();
917 _send_message_sendmail();
921 if ( my $error = $@ ) {
923 $0 has detected an error while trying to send your message: $error.
925 Your message may not have been sent. You will now have a chance to save a copy to disk.
931 1 while unlink($filename); # remove all versions under VMS
937 This program is designed to help you generate and send bug reports
938 (and thank-you notes) about perl5 and the modules which ship with it.
940 In most cases, you can just run "$0" interactively from a command
941 line without any special arguments and follow the prompts.
945 $0 [-v] [-a address] [-s subject] [-b body | -f inpufile ] [ -F outputfile ]
946 [-r returnaddress] [-e editor] [-c adminaddress | -C] [-S] [-t] [-h]
948 $0 [-v] [-r returnaddress] [-A] [-ok | -okay | -nok | -nokay]
953 -v Include Verbose configuration data in the report
954 -f File containing the body of the report. Use this to
955 quickly send a prepared message.
956 -p File containing a patch or other text attachment. Separate
957 multiple files with commas.
958 -F File to output the resulting mail message to, instead of mailing.
959 -S Send without asking for confirmation.
960 -a Address to send the report to. Defaults to '$address'.
961 -c Address to send copy of report to. Defaults to '$cc'.
962 -C Don't send copy to administrator.
963 -s Subject to include with the message. You will be prompted
964 if you don't supply one on the command line.
965 -b Body of the report. If not included on the command line, or
966 in a file with -f, you will get a chance to edit the message.
967 -r Your return address. The program will ask you to confirm
968 this if you don't give it here.
970 -t Test mode. The target address defaults to '$testaddress'.
971 -T Thank-you mode. The target address defaults to '$thanksaddress'.
972 -d Data mode. This prints out your configuration data, without mailing
973 anything. You can use this with -v to get more complete data.
974 -A Don't send a bug received acknowledgement to the return address.
975 -ok Report successful build on this system to perl porters
976 (use alone or with -v). Only use -ok if *everything* was ok:
977 if there were *any* problems at all, use -nok.
978 -okay As -ok but allow report from old builds.
979 -nok Report unsuccessful build on this system to perl porters
980 (use alone or with -v). You must describe what went wrong
981 in the body of the report which you will be asked to edit.
982 -nokay As -nok but allow report from old builds.
983 -h Print this help message.
990 # Good. Use a secure temp file
991 my ($fh, $filename) = File::Temp::tempfile(UNLINK => 1);
995 # Bah. Fall back to doing things less securely.
996 my $dir = File::Spec->tmpdir();
997 $filename = "bugrep0$$";
998 $filename++ while -e File::Spec->catfile($dir, $filename);
999 $filename = File::Spec->catfile($dir, $filename);
1004 my @paragraphs = split /\n{2,}/, "@_";
1005 for (@paragraphs) { # implicit local $_
1013 my ($explanation, $prompt, $default) = (@_);
1016 paraprint $explanation;
1018 print $prompt. ($default ? " [$default]" :''). ": ";
1019 my $result = scalar(<>);
1020 return $default if !defined $result; # got eof
1022 $result =~ s/^\s*(.*?)\s*$/$1/s;
1023 if ($default && $result eq '') {
1034 for my $header (keys %attr) {
1035 $head .= "$header: ".$attr{$header}."\n";
1040 sub _message_headers {
1041 my %headers = ( To => $address, Subject => $subject );
1042 $headers{'Cc'} = $cc if ($cc);
1043 $headers{'Message-Id'} = $messageid if ($messageid);
1044 $headers{'Reply-To'} = $from if ($from);
1045 $headers{'From'} = $from if ($from);
1046 if ($have_attachment) {
1047 $headers{'MIME-Version'} = '1.0';
1048 $headers{'Content-Type'} = qq{multipart/mixed; boundary=\"$mime_boundary\"};
1053 sub _add_body_start {
1054 my $body_start = <<"BODY_START";
1055 This is a multi-part message in MIME format.
1057 Content-Type: text/plain; format=fixed
1058 Content-Transfer-Encoding: 8bit
1064 sub _add_attachments {
1066 for my $attachment (split /\s*,\s*/, $attachments) {
1067 my $attach_file = basename($attachment);
1068 $attach .= <<"ATTACHMENT";
1071 Content-Type: text/x-patch; name="$attach_file"
1072 Content-Transfer-Encoding: 8bit
1073 Content-Disposition: attachment; filename="$attach_file"
1077 open my $attach_fh, '<:raw', $attachment
1078 or die "Couldn't open attachment '$attachment': $!\n";
1079 while (<$attach_fh>) { $attach .= $_; }
1080 close($attach_fh) or die "Error closing attachment '$attachment': $!";
1083 $attach .= "\n--$mime_boundary--\n";
1090 open( REP, "<:raw", $fname ) or die "Couldn't open file '$fname': $!\n";
1091 binmode(REP, ':raw :crlf') if $Is_MSWin32;
1092 # wrap long lines to make sure the report gets delivered
1093 local $Text::Wrap::columns = 900;
1094 local $Text::Wrap::huge = 'overflow';
1096 if ($::HaveWrap && /\S/) { # wrap() would remove empty lines
1097 $content .= Text::Wrap::wrap(undef, undef, $_);
1102 close(REP) or die "Error closing report file '$fname': $!";
1106 sub build_complete_message {
1107 my $content = _build_header(%{_message_headers()}) . "\n\n";
1108 $content .= _add_body_start() if $have_attachment;
1109 $content .= _read_report($filename);
1110 $content .= _add_attachments() if $have_attachment;
1114 sub save_message_to_disk {
1117 open OUTFILE, '>:raw', $file or do { warn "Couldn't open '$file': $!\n"; return undef};
1118 binmode(OUTFILE, ':raw :crlf') if $Is_MSWin32;
1120 print OUTFILE build_complete_message();
1121 close(OUTFILE) or do { warn "Error closing $file: $!"; return undef };
1122 print "\nMessage saved.\n";
1126 sub _send_message_vms {
1128 my $mail_from = $from;
1129 my $rcpt_to_to = $address;
1130 my $rcpt_to_cc = $cc;
1132 map { $_ =~ s/^[^<]*<//;
1133 $_ =~ s/>[^>]*//; } ($mail_from, $rcpt_to_to, $rcpt_to_cc);
1135 if ( open my $sff_fh, '|-:raw', 'MCR TCPIP$SYSTEM:TCPIP$SMTP_SFF.EXE SYS$INPUT:' ) {
1136 print $sff_fh "MAIL FROM:<$mail_from>\n";
1137 print $sff_fh "RCPT TO:<$rcpt_to_to>\n";
1138 print $sff_fh "RCPT TO:<$rcpt_to_cc>\n" if $rcpt_to_cc;
1139 print $sff_fh "DATA\n";
1140 print $sff_fh build_complete_message();
1141 my $success = close $sff_fh;
1143 print "\nMessage sent\n";
1147 die "Mail transport failed (leaving bug report in $filename): $^E\n";
1150 sub _send_message_mailsend {
1151 my $msg = Mail::Send->new();
1152 my %headers = %{_message_headers()};
1153 for my $key ( keys %headers) {
1154 $msg->add($key => $headers{$key});
1158 binmode($fh, ':raw');
1159 print $fh _add_body_start() if $have_attachment;
1160 print $fh _read_report($filename);
1161 print $fh _add_attachments() if $have_attachment;
1162 $fh->close or die "Error sending mail: $!";
1164 print "\nMessage sent.\n";
1167 sub _probe_for_sendmail {
1169 for (qw(/usr/lib/sendmail /usr/sbin/sendmail /usr/ucblib/sendmail)) {
1170 $sendmail = $_, last if -e $_;
1172 if ( $^O eq 'os2' and $sendmail eq "" ) {
1173 my $path = $ENV{PATH};
1175 my @path = split /$Config{'path_sep'}/, $path;
1177 $sendmail = "$_/sendmail", last if -e "$_/sendmail";
1178 $sendmail = "$_/sendmail.exe", last if -e "$_/sendmail.exe";
1184 sub _send_message_sendmail {
1185 my $sendmail = _probe_for_sendmail();
1186 unless ($sendmail) {
1187 my $message_start = !$Is_Linux && !$Is_OpenBSD ? <<'EOT' : <<'EOT';
1188 It appears that there is no program which looks like "sendmail" on
1189 your system and that the Mail::Send library from CPAN isn't available.
1191 It appears that there is no program which looks like "sendmail" on
1194 paraprint(<<"EOF"), die "\n";
1196 Because of this, there's no easy way to automatically send your
1199 A copy of your message has been saved in '$filename' for you to
1200 send to '$address' with your normal mail client.
1204 open( SENDMAIL, "|-:raw", $sendmail, "-t", "-oi", "-f", $from )
1205 || die "'|$sendmail -t -oi -f $from' failed: $!";
1206 print SENDMAIL build_complete_message();
1207 if ( close(SENDMAIL) ) {
1208 print "\nMessage sent\n";
1210 warn "\nSendmail returned status '", $? >> 8, "'\n";
1216 # a strange way to check whether any significant editing
1217 # has been done: check whether any new non-empty lines
1220 sub _fingerprint_lines_in_report {
1222 # read in the report template once so that
1223 # we can track whether the user does any editing.
1224 # yes, *all* whitespace is ignored.
1226 open(REP, '<:raw', $filename) or die "Unable to open report file '$filename': $!\n";
1227 binmode(REP, ':raw :crlf') if $Is_MSWin32;
1228 while (my $line = <REP>) {
1230 $new_lines++ if (!$REP{$line});
1233 close(REP) or die "Error closing report file '$filename': $!";
1234 # returns the number of lines with content that wasn't there when last we looked
1241 ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ~~
1249 perlbug - how to submit bug reports on Perl
1255 B<perlbug> S<[ B<-v> ]> S<[ B<-a> I<address> ]> S<[ B<-s> I<subject> ]>
1256 S<[ B<-b> I<body> | B<-f> I<inputfile> ]> S<[ B<-F> I<outputfile> ]>
1257 S<[ B<-r> I<returnaddress> ]>
1258 S<[ B<-e> I<editor> ]> S<[ B<-c> I<adminaddress> | B<-C> ]>
1259 S<[ B<-S> ]> S<[ B<-t> ]> S<[ B<-d> ]> S<[ B<-A> ]> S<[ B<-h> ]> S<[ B<-T> ]>
1261 B<perlbug> S<[ B<-v> ]> S<[ B<-r> I<returnaddress> ]>
1262 S<[ B<-A> ]> S<[ B<-ok> | B<-okay> | B<-nok> | B<-nokay> ]>
1269 This program is designed to help you generate and send bug reports
1270 (and thank-you notes) about perl5 and the modules which ship with it.
1272 In most cases, you can just run it interactively from a command
1273 line without any special arguments and follow the prompts.
1275 If you have found a bug with a non-standard port (one that was not
1276 part of the I<standard distribution>), a binary distribution, or a
1277 non-core module (such as Tk, DBI, etc), then please see the
1278 documentation that came with that distribution to determine the
1279 correct place to report bugs.
1281 If you are unable to send your report using B<perlbug> (most likely
1282 because your system doesn't have a way to send mail that perlbug
1283 recognizes), you may be able to use this tool to compose your report
1284 and save it to a file which you can then send to B<perlbug@perl.org>
1285 using your regular mail client.
1287 In extreme cases, B<perlbug> may not work well enough on your system
1288 to guide you through composing a bug report. In those cases, you
1289 may be able to use B<perlbug -d> to get system configuration
1290 information to include in a manually composed bug report to
1291 B<perlbug@perl.org>.
1294 When reporting a bug, please run through this checklist:
1298 =item What version of Perl you are running?
1300 Type C<perl -v> at the command line to find out.
1302 =item Are you running the latest released version of perl?
1304 Look at http://www.perl.org/ to find out. If you are not using the
1305 latest released version, please try to replicate your bug on the
1306 latest stable release.
1308 Note that reports about bugs in old versions of Perl, especially
1309 those which indicate you haven't also tested the current stable
1310 release of Perl, are likely to receive less attention from the
1311 volunteers who build and maintain Perl than reports about bugs in
1312 the current release.
1314 This tool isn't appropriate for reporting bugs in any version
1317 =item Are you sure what you have is a bug?
1319 A significant number of the bug reports we get turn out to be
1320 documented features in Perl. Make sure the issue you've run into
1321 isn't intentional by glancing through the documentation that comes
1322 with the Perl distribution.
1324 Given the sheer volume of Perl documentation, this isn't a trivial
1325 undertaking, but if you can point to documentation that suggests
1326 the behaviour you're seeing is I<wrong>, your issue is likely to
1327 receive more attention. You may want to start with B<perldoc>
1328 L<perltrap> for pointers to common traps that new (and experienced)
1329 Perl programmers run into.
1331 If you're unsure of the meaning of an error message you've run
1332 across, B<perldoc> L<perldiag> for an explanation. If the message
1333 isn't in perldiag, it probably isn't generated by Perl. You may
1334 have luck consulting your operating system documentation instead.
1336 If you are on a non-UNIX platform B<perldoc> L<perlport>, as some
1337 features may be unimplemented or work differently.
1339 You may be able to figure out what's going wrong using the Perl
1340 debugger. For information about how to use the debugger B<perldoc>
1343 =item Do you have a proper test case?
1345 The easier it is to reproduce your bug, the more likely it will be
1346 fixed -- if nobody can duplicate your problem, it probably won't be
1349 A good test case has most of these attributes: short, simple code;
1350 few dependencies on external commands, modules, or libraries; no
1351 platform-dependent code (unless it's a platform-specific bug);
1352 clear, simple documentation.
1354 A good test case is almost always a good candidate to be included in
1355 Perl's test suite. If you have the time, consider writing your test case so
1356 that it can be easily included into the standard test suite.
1358 =item Have you included all relevant information?
1360 Be sure to include the B<exact> error messages, if any.
1361 "Perl gave an error" is not an exact error message.
1363 If you get a core dump (or equivalent), you may use a debugger
1364 (B<dbx>, B<gdb>, etc) to produce a stack trace to include in the bug
1367 NOTE: unless your Perl has been compiled with debug info
1368 (often B<-g>), the stack trace is likely to be somewhat hard to use
1369 because it will most probably contain only the function names and not
1370 their arguments. If possible, recompile your Perl with debug info and
1371 reproduce the crash and the stack trace.
1373 =item Can you describe the bug in plain English?
1375 The easier it is to understand a reproducible bug, the more likely
1376 it will be fixed. Any insight you can provide into the problem
1377 will help a great deal. In other words, try to analyze the problem
1378 (to the extent you can) and report your discoveries.
1380 =item Can you fix the bug yourself?
1382 If so, that's great news; bug reports with patches are likely to
1383 receive significantly more attention and interest than those without
1384 patches. Please attach your patch to the report using the C<-p> option.
1385 When sending a patch, create it using C<git format-patch> if possible,
1386 though a unified diff created with C<diff -pu> will do nearly as well.
1388 Your patch may be returned with requests for changes, or requests for more
1389 detailed explanations about your fix.
1391 Here are a few hints for creating high-quality patches:
1393 Make sure the patch is not reversed (the first argument to diff is
1394 typically the original file, the second argument your changed file).
1395 Make sure you test your patch by applying it with C<git am> or the
1396 C<patch> program before you send it on its way. Try to follow the
1397 same style as the code you are trying to patch. Make sure your patch
1398 really does work (C<make test>, if the thing you're patching is covered
1399 by Perl's test suite).
1401 =item Can you use C<perlbug> to submit the report?
1403 B<perlbug> will, amongst other things, ensure your report includes
1404 crucial information about your version of perl. If C<perlbug> is
1405 unable to mail your report after you have typed it in, you may have
1406 to compose the message yourself, add the output produced by C<perlbug
1407 -d> and email it to B<perlbug@perl.org>. If, for some reason, you
1408 cannot run C<perlbug> at all on your system, be sure to include the
1409 entire output produced by running C<perl -V> (note the uppercase V).
1411 Whether you use C<perlbug> or send the email manually, please make
1412 your Subject line informative. "a bug" is not informative. Neither
1413 is "perl crashes" nor is "HELP!!!". These don't help. A compact
1414 description of what's wrong is fine.
1416 =item Can you use C<perlbug> to submit a thank-you note?
1418 Yes, you can do this by either using the C<-T> option, or by invoking
1419 the program as C<perlthanks>. Thank-you notes are good. It makes people
1424 Having done your bit, please be prepared to wait, to be told the
1425 bug is in your code, or possibly to get no reply at all. The
1426 volunteers who maintain Perl are busy folks, so if your problem is
1427 an obvious bug in your own code, is difficult to understand or is
1428 a duplicate of an existing report, you may not receive a personal
1431 If it is important to you that your bug be fixed, do monitor the
1432 perl5-porters@perl.org mailing list (mailing lists are moderated, your
1433 message may take a while to show up) and the commit logs to development
1434 versions of Perl, and encourage the maintainers with kind words or
1435 offers of frosty beverages. (Please do be kind to the maintainers.
1436 Harassing or flaming them is likely to have the opposite effect of the
1439 Feel free to update the ticket about your bug on http://rt.perl.org
1440 if a new version of Perl is released and your bug is still present.
1448 Address to send the report to. Defaults to B<perlbug@perl.org>.
1452 Don't send a bug received acknowledgement to the reply address.
1453 Generally it is only a sensible to use this option if you are a
1454 perl maintainer actively watching perl porters for your message to
1459 Body of the report. If not included on the command line, or
1460 in a file with B<-f>, you will get a chance to edit the message.
1464 Don't send copy to administrator.
1468 Address to send copy of report to. Defaults to the address of the
1469 local perl administrator (recorded when perl was built).
1473 Data mode (the default if you redirect or pipe output). This prints out
1474 your configuration data, without mailing anything. You can use this
1475 with B<-v> to get more complete data.
1483 File containing the body of the report. Use this to quickly send a
1488 File to output the results to instead of sending as an email. Useful
1489 particularly when running perlbug on a machine with no direct internet
1494 Prints a brief summary of the options.
1498 Report successful build on this system to perl porters. Forces B<-S>
1499 and B<-C>. Forces and supplies values for B<-s> and B<-b>. Only
1500 prompts for a return address if it cannot guess it (for use with
1501 B<make>). Honors return address specified with B<-r>. You can use this
1502 with B<-v> to get more complete data. Only makes a report if this
1503 system is less than 60 days old.
1507 As B<-ok> except it will report on older systems.
1511 Report unsuccessful build on this system. Forces B<-C>. Forces and
1512 supplies a value for B<-s>, then requires you to edit the report
1513 and say what went wrong. Alternatively, a prepared report may be
1514 supplied using B<-f>. Only prompts for a return address if it
1515 cannot guess it (for use with B<make>). Honors return address
1516 specified with B<-r>. You can use this with B<-v> to get more
1517 complete data. Only makes a report if this system is less than 60
1522 As B<-nok> except it will report on older systems.
1526 The names of one or more patch files or other text attachments to be
1527 included with the report. Multiple files must be separated with commas.
1531 Your return address. The program will ask you to confirm its default
1532 if you don't use this option.
1536 Send without asking for confirmation.
1540 Subject to include with the message. You will be prompted if you don't
1541 supply one on the command line.
1545 Test mode. The target address defaults to B<perlbug-test@perl.org>.
1546 Also makes it possible to command perlbug from a pipe or file, for
1551 Send a thank-you note instead of a bug report.
1555 Include verbose configuration data in the report.
1561 Kenneth Albanowski (E<lt>kjahds@kjahds.comE<gt>), subsequently
1562 I<doc>tored by Gurusamy Sarathy (E<lt>gsar@activestate.comE<gt>),
1563 Tom Christiansen (E<lt>tchrist@perl.comE<gt>), Nathan Torkington
1564 (E<lt>gnat@frii.comE<gt>), Charles F. Randall (E<lt>cfr@pobox.comE<gt>),
1565 Mike Guy (E<lt>mjtg@cam.ac.ukE<gt>), Dominic Dunlop
1566 (E<lt>domo@computer.orgE<gt>), Hugo van der Sanden (E<lt>hv@crypt.orgE<gt>),
1567 Jarkko Hietaniemi (E<lt>jhi@iki.fiE<gt>), Chris Nandor
1568 (E<lt>pudge@pobox.comE<gt>), Jon Orwant (E<lt>orwant@media.mit.eduE<gt>,
1569 Richard Foley (E<lt>richard.foley@rfi.netE<gt>), Jesse Vincent
1570 (E<lt>jesse@bestpractical.comE<gt>), and Craig A. Berry (E<lt>craigberry@mac.comE<gt>).
1574 perl(1), perldebug(1), perldiag(1), perlport(1), perltrap(1),
1575 diff(1), patch(1), dbx(1), gdb(1)
1579 None known (guess what must have been used to report them?)
1585 close OUT or die "Can't close $file: $!";
1586 chmod 0755, $file or die "Can't reset permissions for $file: $!\n";
1587 exec("$Config{'eunicefix'} $file") if $Config{'eunicefix'} ne ':';