On linux I can do DISPLAY="" perl -d test.pl which will only use 1 xterm:
xterm: DISPLAY is not set ######### Forked, but do not know how to create a new TTY. ######### Since two debuggers fight for the same TTY, input is severely entang +led. I know how to switch the output to a different window in xterms and OS/2 consoles only. For a manual switch, put the name of the cr +eated TTY in $DB::fork_TTY, or define a function DB::get_fork_TTY() returning +this. On UNIX-like systems one can get the name of a TTY for the given win +dow by typing tty, and disconnect the shell from TTY by sleep 1000000.

I get mixed output/input from the different processes, though, so it's probably not very useful to run the program like this :-)


In reply to Re: perl debugger and forking by Joost
in thread perl debugger and forking by beemshake

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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! —
  • 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:
    & &amp;
    < &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.