> show modified variables values each time n, s debug step is done ?
Have a look at < and { command family, IIRC you can tell them what to do for each prompt while stepping thru code
update
DB<1> h >
? List Perl commands to run after each prompt.
expr Define Perl command to run after each prompt.
> expr Add to the list of Perl commands to run after each promp
+t.
* Delete the list of Perl commands to run after each prompt.
DB<2> h }
is not a debugger command.
DB<3> h {
db_command Define debugger command to run before each prompt.
? List debugger commands to run before each prompt.
{ db_command Add to the list of debugger commands to run before eac
+h prompt.
* Delete the list of debugger commands to run before each
+ prompt.
DB<4> h <
? List Perl commands to run before each prompt.
expr Define Perl command to run before each prompt.
< expr Add to the list of Perl commands to run before each prom
+pt.
* Delete the list of perl commands to run before each
+prompt.
DB<5>
"Perl commands" => Perl code
"debugger commands" => those one letter commands listed with h h
-
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.
|