I've got the following subroutine working relatively well for debugging forking processes in a screen session.

I'd like to submit it to whoever is maintaining the perl5db.pl file, or at least to rt.cpan.org. But before I do that, I'd like to make it as robust as possible.

I wasn't sure where else to put this--and since this is a request for the collective wisdom to evaluate the code this seemed as best a place as any. Please let me know if you think this can go better elsewhere.

Please note the following:

Here's the subroutine:
sub DB::get_fork_TTY { require File::Temp or return ''; my ( $FH, $filename ) = File::Temp::tempfile( UNLINK => 1 ); system( qq{screen -t 'Child $$' sh -c "tty > $filename ; sleep 10000 +00"} ) == 0 or return ''; chomp ( my $tty = <$FH> ); return $tty; }
And the test code I've been using it on:
#!/usr/bin/perl -w use strict; sub DB::get_fork_TTY { require File::Temp or return ''; my ( $FH, $filename ) = File::Temp::tempfile( UNLINK => 1 ); system( qq{screen -t 'Child $$' sh -c "tty > $filename ; sleep 10000 +00"} ) == 0 or return ''; chomp ( my $tty = <$FH> ); return $tty; } if ( my $child = fork ) { $DB::single = 1; print "We're in the parent! ($child)\n"; } else { die "Can't fork" unless defined $child; $DB::single = 1; print "We're in the child!\n"; } exit;
Added check for failed fork as suggested
Harley J Pig

In reply to Debugging forking scripts in screen by harleypig

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.