I'm encountering what looks like a bug in scsh, and I was hoping I might get
some help here in tracking it down.
It's easy to describe: sometimes scsh forks a subprocess and never comes
back. In particular, I'm doing a run/string on a program which may or may
not produce any output. In most cases, things work OK but in a sizable
fraction (say 10%) scsh appears to hang. The forked process terminates, but
scsh never returns. It also does not respond to signals, e.g. Keyboard
I have not had much time to dig into this, but I did try sticking a printf
in the signal handler installed by scsh. When a keyboard interrupt arrives,
scsh is getting the signal and printing my message. Also, I put a printf in
the loop which calls select() (sorry, don't have the filename handy) and I
see that the loop continues to run. It looks like it's waiting for an event
which never arrives.
This is on linux 2.4 with an SMP kernel, if that has anything to do with it.
Any ideas on where I could look for the problem? Also, it's certainly
possible that the program being run by scsh is not behaving "correctly"
somehow, but still ...