From: Jay Hannah Date: Fri, 24 Jan 2003 11:28:44 +0000 (-0600) Subject: RE: perldebug.pod suggestion X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=bea985324a3cd895f8e0a0c38e90ab3d09433415;p=p5sagit%2Fp5-mst-13.2.git RE: perldebug.pod suggestion From: "Jay Hannah" Message-ID: <00b001c2c3ce$0c4716e0$4709a8c0@omarests2> p4raw-id: //depot/perl@18683 --- diff --git a/pod/perldebug.pod b/pod/perldebug.pod index dafa572..8d2e42c 100644 --- a/pod/perldebug.pod +++ b/pod/perldebug.pod @@ -891,6 +891,15 @@ in by Perl and may contain arbitrary commands, for security reasons, it must be owned by the superuser or the current user, and writable by no one but its owner. +You can mock TTY input to debugger by adding arbitrary commands to +@DB::typeahead. For example, your F<.perldb> file might contain: + + sub afterinit { push @DB::typeahead, "b 4", "b 6"; } + +Which would attempt to set breakpoints on lines 4 and 6 immediately +after debugger initilization. Note that @DB::typeahead is not a supported +interface and is subject to change in future releases. + If you want to modify the debugger, copy F from the Perl library to another name and hack it to your heart's content. You'll then want to set your C environment variable to say