in reply to weird ctrl-z behaviour when piping from tin through perl

Also, what about just trying to stop a perl program by itself. Can you ^Z 
perl -pel

[download]
(thx to ikegami for the brevity advice). If this also fails, then the problem may be your build of perl. I noticed a gcc-related problem reported against netbsd and perl signal handling that could possibly be relevant...

Replies are listed 'Best First'.
Re^2: weird ctrl-z behaviour when piping from tin through perl
by Anonymous Monk on Sep 12, 2009 at 22:09 UTC

    If I pipe through perl -pel directly, then I can suspend and get a shell prompt. That's slightly different though, because the perl process has already finished by then and it's just the tin prompt Press <RETURN> to continue... that I'm suspending from (sorry, I'm not fast enough to interrupt perl justing printing its input).

    Thanks for the link; however, the NetBSD version comes with gcc (GCC) 4.1.3 20080202 prerelease (NetBSD nb1 20080202).

[reply]
[d/l]
[select]
      Sorry, but that is not what I asked. Just type 
      perl -pel

      [download]
      from the shell prompt. This should simply allow you to type a line (with no echo), and see what you typed every time you hit enter. It should not end until you hit ctrl-C. At this point, what happens when you type ctrl-Z? If it suspends properly, then I would have to assume that it is some problem dealing with process-group signaling in NetBSD. If it does not suspend properly, then your build of perl is the problem.
[reply]
[d/l]

        Ah, sorry, I misunderstood. 

        # perl -pel
la
la
^Z
[1]+ Stopped             perl -pel
#

        [download]
        So your suggestion is that there's some problem with process-group signaling. Any hints on example code that might break, or where in perl's code I should look, or other suggestions?

        Thank you.

[reply]
[d/l]

In Section Seekers of Perl Wisdom