Can you do what they suggest in Debugger Customization?
Edit: To be specific, you want to implement a .perldb file, with the afterinit subroutine that pushes commands to the @DB:typeahead array. You might want to try something like the following (untested):
#This is your .perldb file, it lives in ~/.perldb or ./.perldb, as per
+ [perldebug].
#Create a file of your debugger commands (one per line) and save it so
+mewhere. Put its location in the environment variable PERLDB_MYCOMMAN
+DFILE.
BEGIN {
sub afterinit {
if ( $ENV{PERLDB_MYCOMMANDFILE} && -e $ENV{PERLDB_MYCOMMANDFIL
+E}) {
warn "Running commands from $ENV{PERLDB_MYCOMMANDFILE}";
open my $cmdfile, "<", $ENV{PERLDB_MYCOMMANDFILE} or die "
+can't open $ENV{PERLDB_MYCOMMANDFILE}: $!";
push @DB::typeahead, <$cmdfile>;
close $cmdfile;
}
}
}
- Thomas
"Excuse me for butting in, but I'm interrupt-driven..."
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|