65 which lets the debugger get control inside of C<eval>'ed code. The debugger
66 localizes a saved copy of C<$@> inside the subroutine, which allows it to
67 keep C<$@> safe until it C<DB::eval> returns, at which point the previous
69 track of C<$@> inside C<eval>s which C<eval> other C<eval's>.
140 probably have to benchmark alternate implementations and see which is the
338 which is called before every statement, checks this and puts the user into
469 package. This is because there are several BEGIN blocks (which of course 
517 local lexical, localize C<$saved[0]> (which is where C<save()> will put 
783 #   + Added message if you clear your pre/post command stacks which was
786 #     API is fundamentally screwed up; likewise option setting, which
920 warnings during its own compilation, defining variables which it will need
1092 There are a number of initialization-related variables which can be set
1114 =item C<$CommandSet> - which command set to use (defaults to new, documented set)
1270 # your lexical scope, which is unfortunate at best.
1330 The last thing we do during initialization is determine which subroutine is
1355 # untaint $^O, which may have been tainted by the last statement.
1690 Note that the order in which the commands are processed is very important;
1810 function which will be run on each entry to C<DB::DB>; it gets the 
2451 demarcation' above which commands can be entered anytime, and below which
2456 Done by setting C<$single> to 2, which forces subs to execute straight through
2474 Sets C<$single> to 1, which causes X<DB::sub> to continue tracing inside     
2494 breakpoint, which is either a subroutine name or a line number. We set
2558                     # for an executable, which we may or may not have found.
2560                     # If $i (which we set $subname from) is non-zero, we
2648                     # out of it (except for the first one, which is going
2987 Manages the commands in C<@hist> (which is created if C<Term::ReadLine> reports
3168                         # as separators (which is why we escaped them in 
3261 is the C<|> command, we also set up a C<SIGPIPE> handler which will simply 
3530 arguments with which the subroutine was invoked
3687 Support functions in this section which have multiple modes of failure C<die> 
3738 (which means external entities can't fiddle with it) and create the name of 
3827     # if delete_action blows up for some reason, in which case
3993 We take the file passed in and try to find it in C<%INC> (which maps modules
4039 The second function is a wrapper which does the following:
4415 which lists all currently-loaded files which have breakpoints. We then look
4677         # swap it to 'start+', which will list a window from the start point.
4784 first. It starts a C<%had_breakpoints>, which tells us what all files have
4969     # which means that we'll always enter this loop (though a non-numeric
5013         # in the user's context. This version can handle expressions which
5266 It gets a filehandle (to which C<dumpvar.pl>'s output will be directed) and
5349 C<dump_trace> routine, which actually does all the ferreting-out of the
5456 =item * C<file> - the file in which this item was defined (if any)
5458 =item * C<line> - the line on which it was defined
5623 Of note is the definition of the $balanced_brace_re global via ||=, which
5789     # XXX Ornaments are turned on unconditionally, which is not
5798 via C<system()> which starts a new debugger, we need to be able to get a new
5803 C<get_fork_TTY> is a glob-aliased function which calls the real function that 
5808 The debugger provides C<get_fork_TTY> functions which work for X Windows and
5810 C<get_fork_TTY> functions which work for I<your> platform and contribute them.
5820 command (which prints the device name of the TTY we'll want to use for input 
5822 to file number 3. This way we can simply read from the <XT> filehandle (which
6235         # They're going for a default, which we assume is 1.
6631 Sets the recall command, and builds a printable version which will appear in
6732 easy to parse and portable, but which still allows the help to be a little
7293     # We can call Carp::longmess without its being "debugged" (which we 
7454 L<Devel::Peek> to try to find the glob in which this code reference lives
7455 (if it does) - this allows us to actually code references which correspond
7552 try; C<$prefix> is the message prefix, which gets built up as we go up the
7596 =head2 C<setman> - figure out which command to use to show documentation
7737     # This defines the point at which you get the 'deep recursion' 
7877 the subpackages against the text, and discarding all of them which 
7907         # We might possibly want to switch to an eval (which has a "filename"
8056 question mark, which, if executed, will list the current value of the option.
8093         # If there were multiple possible values, return '? ', which
8158 We then call C<DB::fake::at_exit()>, which returns the C<Use 'q' to quit ...">
8485     my $which = '';
8494         $which = 'pre-perl';
8500         $which = 'post-perl';
8513             $which = 'pre-debugger';
8519     unless ($which) {
8529                 print $OUT "No $which actions.\n";
8533                 print $OUT "$which commands:\n";
8561                   "Confused by strange length of $which command($cmd)...\n";

Indexes created Tue Jul 24 14:28:13 CEST 2018