On 08/29/11 01:26, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>> The example opens up a tcsh prompt.
> See, that's gotta be a bug, right there! ;-)
>
You're right, it is a bug.. in bash!
During dev, I was getting inconsistent behavior from bash
on an old OSX 10.4.11 system; both the bash and ksh on that
system would suspend itself when both input and output were pipes.
At first I thought it was my app, but could replicate from the cli:
# echo echo hello | sh -is 2>&1 | cat
[1]+ Stopped(SIGTTIN) echo echo hello | sh -is 2>&1 | cat
^^
Heh?
# fg
echo echo hello | sh -is 2>&1 | cat
[1]+ Stopped(SIGTTIN) echo echo hello | sh -is 2>&1 | cat
^^
wat
# fg
echo echo hello | sh -is 2>&1 | cat
[1]+ Stopped(SIGTTIN) echo echo hello | sh -is 2>&1 | cat
^^
Won't go away!
# ps aux | grep sh..is | grep -v grep
root 2980 0.0 0.1 27812 552 p2 S 6:07AM 0:00.01 sh -is
# kill -9 2980 <-- kills it, finally
# sw_vers
ProductName: Mac OS X
ProductVersion: 10.4.11
BuildVersion: 8S165
This was pretty bad, cause the app would get no prompt,
and the sh was bg'ed in the invoking shell, and would remain
until killed.
Perhaps fixed in an update, but I didn't want folks running
into that. tcsh worked fine, so I left that in.
I've run into a lot of weird bugs on OSX with unix stuff..
really unsettling.
_______________________________________________
fltk-dev mailing list
fltk-dev@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-dev
