in reply to Re^2: Threads Printing Issue - Output Mangled / Term Crashing
in thread Threads Printing Issue - Output Mangled / Term Crashing

Then, and easy workaround is to write a wrapper for tcpdump that launches it and then kills it when stdin is closed: 
#!/usr/bin/perl
# untested:

require POSIX;
my $pid = fork;
unless ($pid) {
    exec 'tcpdump', @ARGV;
    POSIX::_exit(1);
}
while (<>) { ; }; # just discard input until EOF
kill KILL => $pid;

[download]
You will have to place the wrapper on the remote machines (or just make it into a perl one-liner and pass it on the ssh call)

Replies are listed 'Best First'.
Re^4: Threads Printing Issue - Output Mangled / Term Crashing
by bigbot (Beadle) on Apr 14, 2014 at 12:21 UTC
    But do you think the SSH -t options are what's causing the issue?
[reply]
      I don't see any error on your code so I blame the unknown! :-)

      Now seriously, yes, the TTY handling code in OpenSSH is quite hairy and bugs there are not so uncommon as one would like.

[reply]
        OK great suggestion I should have thought of this sooner. It was the only option I changed in the SSH line and that was most likely causing the issue. I just find it weird that simply putting that output in a variable can mess up your local prompt.
[reply]

In Section Seekers of Perl Wisdom