[net.bugs.4bsd] 4.2 csh signal related bug

phil@sequent.UUCP (02/26/84)

        I have on occasion run across what I believe to be a  bug
in  4.2  csh.  The  symptoms are that when you type a command and
hit return it starts up the program but  immediately  blurbs  out
some message about "Reset pgrp from # to #" and sends a Hangup to
the process.  Once this occurs you are  hosed  although  you  can
sometimes  get a few things to run (ie, you can type ls and 1 out
of 5 times it runs without the Reset message).

As near as I can tell, this behaviour occurs just  around  either
having  just typed ^Z or my interrupt character which leads me to
believe it may be a signal related problem.  Two  questions,  why 
does  this  only  happen to me (nobody else here has seen it) and
what is it?
-- 

	Phil Hochstetler
	Sequent Computer Systems
	...!sequent!phil

faustus@ucbvax.UUCP (Wayne Christopher) (02/26/84)

As far as I can tell that only happens when you redirect the
output of a process to a builtin that doesn't accept input, i.e.

cat | cd

Can you give examples of how this happens otherwise (as the
result of signals)?

	Wayne

padpowell@wateng.UUCP (PAD Powell [Admin]) (02/26/84)

<bug>
	From phil@sequent.UUCP Wed Dec 31 19:00:00 1969
	Subject: 4.2 csh signal related bug

	        I have on occasion run across what I believe to be a  bug
	in  4.2  csh.  The  symptoms are that when you type a command and
	hit return it starts up the program but  immediately  blurbs  out
	some message about "Reset pgrp from # to #" and sends a Hangup to
	the process.  Once this occurs you are  hosed  although  you  can
	sometimes  get a few things to run (ie, you can type ls and 1 out
	of 5 times it runs without the Reset message).
	
	As near as I can tell, this behaviour occurs just  around  either
	having  just typed ^Z or my interrupt character which leads me to
	believe it may be a signal related problem.  Two  questions,  why 
	does  this  only  happen to me (nobody else here has seen it) and
	what is it?
	
I have observed this under 4.1 csh also.  The following erroneous
input, combined with hitting "break" while it is printing error messages
seems to cause the same effect.

repeat 10 (fortune; sleep 10)

Interesting, eh?

Patrick Powell

dce@hammer.UUCP (03/03/84)

This problem is stranger than you think. I can type 'ls | echo'
and get the same message, but I can still type commands.

This problem also occurred in 4.1cBSD. Someone here also mentioned
that this happens to them when they break out of a 'repeat' in csh.

			David