Thanks, I can do that. But when this occurs it happens thousands of times in a row and chomps up lots of CPU. Is there a way to diagnose what's occurring? Where the signal is coming from etc?
I still dont' know why the command line version of this program complains about bad file descriptor.