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/

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.