summaryrefslogtreecommitdiff
path: root/lib/perl5db.pl
diff options
context:
space:
mode:
authorDuke Leto <jonathan@leto.net>2009-06-04 01:22:46 -0700
committerDuke Leto <jonathan@leto.net>2009-06-04 01:22:46 -0700
commitb468dcb6f9226d3227926224976100d835ba9dda (patch)
tree5a270a130707b88e3cc05d21c1823746c1df3178 /lib/perl5db.pl
parentf96342d4d75c8fb34f1848985bba33c57b699e85 (diff)
downloadperl-b468dcb6f9226d3227926224976100d835ba9dda.tar.gz
Bump version of perl5db.pl to 1.33, add changelog comments and fix a POD typo
Diffstat (limited to 'lib/perl5db.pl')
-rw-r--r--lib/perl5db.pl8
1 files changed, 6 insertions, 2 deletions
diff --git a/lib/perl5db.pl b/lib/perl5db.pl
index da29b9e54d..e7ec200234 100644
--- a/lib/perl5db.pl
+++ b/lib/perl5db.pl
@@ -511,7 +511,7 @@ package DB;
BEGIN {eval 'use IO::Handle'}; # Needed for flush only? breaks under miniperl
# Debugger for Perl 5.00x; perl5db.pl patch level:
-$VERSION = 1.32;
+$VERSION = '1.33';
$header = "perl5db.pl version $VERSION";
@@ -949,6 +949,9 @@ sub eval {
# + [perl #57016] debugger: o warn=0 die=0 ignored
# + Note, but don't use, PERLDBf_SAVESRC
# + Fix #7013: lvalue subs not working inside debugger
+# Changes: 1.32: Jun 03, 2009 Jonathan Leto <jonathan@leto.net>
+# + Fix bug where a key _< with undefined value was put into the symbol table
+# + when the $filename variable is not set
########################################################################
=head1 DEBUGGER INITIALIZATION
@@ -1053,6 +1056,7 @@ warn( # Do not ;-)
)
if 0;
+# without threads, $filename is not defined until DB::sub is called
foreach my $k (keys (%INC)) {
&share(\$main::{'_<'.$filename}) if defined $filename;
};
@@ -1846,7 +1850,7 @@ $I_m_init = 1;
This gigantic subroutine is the heart of the debugger. Called before every
statement, its job is to determine if a breakpoint has been reached, and
stop if so; read commands from the user, parse them, and execute
-them, and hen send execution off to the next statement.
+them, and then send execution off to the next statement.
Note that the order in which the commands are processed is very important;
some commands earlier in the loop will actually alter the C<$cmd> variable