note pemungkah You should be able to define the subs you mention in .perldb (either in the current directory, or in ~/.perldb on Unix-like systems). Quoting the debugger's internal docs (<code>perldoc perl5db.pl</code>): <blockquote> When <code>perl5db.pl</code> starts, it reads an rcfile (<code>perl5db.ini</code> for non-interactive sessions, <code>.perldb</code> for interactive ones) that can set a number of options. In addition, this file may define a subroutine <code>afterinit</code> that will be executed (in the debugger's context) after the debugger has initialized itself. This can be set in the options, or by setting it in <code>.perldb</code>. </blockquote> <code>afterinit()</code> runs a little too late - <i>after</i> TTY allocation - so you can't do the TTY mojo there. However, <code>.perldb</code> gets control right after option processing, and just <i>before</i> the <code>get_fork_TTY</code> subroutine is checked for and called, so it's an optimum point to set this up if you don't want to use another module to do it. <p> You can of course <code>use</code> a module that defines <code>DB::get_fork_TTY</code> in <code>.perldb</code> as well, if you prefer to have all your magic in one place, so to speak. <p> Another item of note is the <code>$DB::CreateTTY</code> variable, which controls when the debugger decides to try grabbing a new TTY (this is a bit-field scalar, so if you want more than one option, you sum them): <ul><li>1 - on <code>fork()</code></li> <li>2 - when debugger is started inside the debugger</li> <li>4 - on startup</li></ul> This lets you decide when you want (and when you don't want) the debugger to try grabbing another TTY. The default is 3 (on fork, and on nest). 128283 128283