summaryrefslogtreecommitdiff
path: root/Master/tlpkg/tlperl/lib/pods/perldebug.pod
diff options
context:
space:
mode:
Diffstat (limited to 'Master/tlpkg/tlperl/lib/pods/perldebug.pod')
-rw-r--r--Master/tlpkg/tlperl/lib/pods/perldebug.pod37
1 files changed, 19 insertions, 18 deletions
diff --git a/Master/tlpkg/tlperl/lib/pods/perldebug.pod b/Master/tlpkg/tlperl/lib/pods/perldebug.pod
index 9e67b4df422..8fbb2312ad4 100644
--- a/Master/tlpkg/tlperl/lib/pods/perldebug.pod
+++ b/Master/tlpkg/tlperl/lib/pods/perldebug.pod
@@ -9,7 +9,7 @@ First of all, have you tried using the B<-w> switch?
If you're new to the Perl debugger, you may prefer to read
-L<perldebtut>, which is a tutorial introduction to the debugger .
+L<perldebtut>, which is a tutorial introduction to the debugger.
=head1 The Perl Debugger
@@ -54,7 +54,7 @@ function with something that doesn't look like a debugger command, such
as a leading C<;> or perhaps a C<+>, or by wrapping it with parentheses
or braces.
-=head2 Calling the debugger
+=head2 Calling the Debugger
There are several ways to call the debugger:
@@ -388,7 +388,7 @@ Delete all watch-expressions.
=item o
X<debugger command, o>
-Display all options
+Display all options.
=item o booloption ...
X<debugger command, o>
@@ -589,7 +589,7 @@ blessed object, or to a package name.
=item M
X<debugger command, M>
-Displays all loaded modules and their versions
+Display all loaded modules and their versions.
=item man [manpage]
@@ -654,7 +654,7 @@ X<debugger option, dieLevel>
Level of verbosity. By default, the debugger leaves your exceptions
and warnings alone, because altering them can break correctly running
programs. It will attempt to print a message when uncaught INT, BUS, or
-SEGV signals arrive. (But see the mention of signals in L<BUGS> below.)
+SEGV signals arrive. (But see the mention of signals in L</BUGS> below.)
To disable this default safe mode, set these values to something higher
than 0. At a level of 1, you get backtraces upon receiving any kind
@@ -876,7 +876,7 @@ corresponds to F</dev/ttyXX>, say, by issuing a command like
See L<perldebguts/"Debugger Internals"> for details.
-=head2 Debugger input/output
+=head2 Debugger Input/Output
=over 8
@@ -942,7 +942,7 @@ also from I<camel_flea>, but from line 4.
If you execute the C<T> command from inside an active C<use>
statement, the backtrace will contain both a C<require> frame and
-an C<eval>) frame.
+an C<eval> frame.
=item Line Listing Format
@@ -977,12 +977,12 @@ for incredibly long examples of these.
=back
-=head2 Debugging compile-time statements
+=head2 Debugging Compile-Time Statements
If you have compile-time executable statements (such as code within
BEGIN, UNITCHECK and CHECK blocks or C<use> statements), these will
I<not> be stopped by debugger, although C<require>s and INIT blocks
-will, and compile-time statements can be traced with C<AutoTrace>
+will, and compile-time statements can be traced with the C<AutoTrace>
option set in C<PERLDB_OPTS>). From your own Perl code, however, you
can transfer control back to the debugger using the following
statement, which is harmless if the debugger is not running:
@@ -1007,7 +1007,7 @@ compile subname> for the same purpose.
The debugger probably contains enough configuration hooks that you
won't ever have to modify it yourself. You may change the behaviour
-of debugger from within the debugger using its C<o> command, from
+of the debugger from within the debugger using its C<o> command, from
the command line via the C<PERLDB_OPTS> environment variable, and
from customization files.
@@ -1056,13 +1056,13 @@ Note that any variables and functions that are not documented in
this document (or in L<perldebguts>) are considered for internal
use only, and as such are subject to change without notice.
-=head2 Readline Support / History in the debugger
+=head2 Readline Support / History in the Debugger
As shipped, the only command-line history supplied is a simplistic one
that checks for leading exclamation points. However, if you install
the Term::ReadKey and Term::ReadLine modules from CPAN (such as
Term::ReadLine::Gnu, Term::ReadLine::Perl, ...) you will
-have full editing capabilities much like GNU I<readline>(3) provides.
+have full editing capabilities much like those GNU I<readline>(3) provides.
Look for these in the F<modules/by-module/Term> directory on CPAN.
These do not support normal B<vi> command-line editing, however.
@@ -1080,9 +1080,10 @@ it can interact with the Perl debugger to provide an integrated
software development environment reminiscent of its interactions
with C debuggers.
-Perl comes with a start file for making B<emacs> act like a
+Recent versions of Emacs come with a
+start file for making B<emacs> act like a
syntax-directed editor that understands (some of) Perl's syntax.
-Look in the I<emacs> directory of the Perl source distribution.
+See L<perlfaq3>.
A similar setup by Tom Christiansen for interacting with any
vendor-shipped B<vi> and the X11 window system is also available.
@@ -1117,7 +1118,7 @@ interpret the information in that profile. More powerful profilers,
such as C<Devel::NYTProf> are available from the CPAN: see L<perlperf>
for details.
-=head1 Debugging regular expressions
+=head1 Debugging Regular Expressions
X<regular expression, debugging>
X<regex, debugging> X<regexp, debugging>
@@ -1127,15 +1128,15 @@ voluminous output, one must not only have some idea about how regular
expression matching works in general, but also know how Perl's regular
expressions are internally compiled into an automaton. These matters
are explored in some detail in
-L<perldebguts/"Debugging regular expressions">.
+L<perldebguts/"Debugging Regular Expressions">.
-=head1 Debugging memory usage
+=head1 Debugging Memory Usage
X<memory usage>
Perl contains internal support for reporting its own memory usage,
but this is a fairly advanced concept that requires some understanding
of how memory allocation works.
-See L<perldebguts/"Debugging Perl memory usage"> for the details.
+See L<perldebguts/"Debugging Perl Memory Usage"> for the details.
=head1 SEE ALSO