Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Apr 96 11:11:09 MDT
From:      Greg Lehey <lehey.pad@sni.de>
To:        jkh@time.cdrom.com (Jordan K. Hubbard)
Cc:        ports@freebsd.org
Subject:   Re: Interesting bash bug - anyone else see this?
Message-ID:  <199604160912.LAA29444@nixpbe.pdb.sni.de>
In-Reply-To: <199604150138.SAA16211@time.cdrom.com>; from "Jordan K. Hubbard" at Apr 14, 96 6:38 pm

next in thread | previous in thread | raw e-mail | index | archive | help
>
> I just noticed it, myself.  It doesn't happen in sh or csh, so it's
> definitely one for -bash and -current (if not also -stable; I dunno!).
>
> <go to a directory with many files in it>
> root@reason-> ls -lt | more
> ^Z
> [2]+  Done                    ls -lt | more
> root@reason-> fg
> ls -lt | more
> Broken pipe
>
> Bug #1: Upon suspending, bash erroneously reports the background job's status
> 	as "Done", not "Suspended"
>
> Bug #2: Upon resuming, we're hosed - the pipe breaks.
>
> Note that this does NOT occur once ls actually starts filling the pipe,
> then you can background and foreground it all day long and nothing bad
> happens.

FWIW, I've tried this on an SNI box (System V.4, R4400).  It does much
the same thing, except that it needs a ^C to get a prompt after the
^Z.  Looks like it isn't a FreeBSD problem.

Greg



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604160912.LAA29444>