Okay, we're stumped. I will fully preface this by saying that we vaguely think this is a windows problem, as opposed to a perl problem. But it's the perl program where the error manifests, so I'm posting here. I'm a unix guy, not a windows guy, so I'm clueless.
Basically, we have several scripts that we run in the windows terminal. From time to time (and yes, this is a mandelbug), the program stops giving us output to the terminal screen. First time this happened, we thought the program was hanging, so tried to kill it with a control-c. And, surprise surprise, it actually lept back to life and spit out the last of its output. Turns out the thing had finished a while ago.
And that's how it works. Sometimes (we're not sure when), the program stops giving us output, but a control-C will "wake it up" and cause it to continue on and display. We're not doing anything fancy with signal handlers or anything in the scripts. This also appears to have started manifesting itself in scripts that didn't previously exhibit the behavior.
So, in short, WTF? Has anyone encountered anything like this? What should we do now?
Update w/more info: It's perl 5.8.8 built for MSWin32-x86-multi-thread, binary build 817  provided by ActiveState, built Mar 20 2006 17:54:25. Microsoft Windows [Version 5.2.3790] is the banner at the top of the terminal, Its Windows Server 2003 Enterprise Edition, Service Pak 1.