Hm... I think so. I just had to do some research to find out how to overcome the terminal from taking over the input/output of the debugger.
You have to do the following:
- Figure out what your debug options will be and either write the options to the .perldb file or add it to the PERLDB_OPTS environment variable like so:
-
.perldb
parse_options("TTY=/dev/ttyp3 LineInfo=/dev/ttyp4 ReadLine=1");
-
terminal
PERLDB_OPTS="TTY=/dev/ttyp3 LineInfo=/dev/ttyp4 ReadLine=1" perl -d your_script.pl
- TTY is the terminal you want to debug in.
- LineInfo is the terminal you want to see the output of your script in
- ReadLine signals that you want to step through your script
-
Though for the whole thing to work you have to send the terminal you want to debug in to sleep before you start to debug. I.e. Go to ttyp3 and give it a command of sleep 1000000.
/oliver/
-
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.
|
