Date: Tue, 6 Aug 2002 18:28:57 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: Christian Weisgerber <naddy@mips.inka.de> Cc: freebsd-current@freebsd.org Subject: Re: Signals/jobs weirdness? Message-ID: <Pine.BSF.4.21.0208061828020.65715-100000@InterJet.elischer.org> In-Reply-To: <aipjlf$51b$1@kemoauc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 6 Aug 2002, Christian Weisgerber wrote: > Christian Weisgerber <naddy@mips.inka.de> wrote: > > > Neither /bin/tcsh nor the pdksh port are affected, so I assume this > > is a problem in bash-2.05b. > > I just rebuilt the 2002-08-01 revision of the port (bash-2.05a), > same effect. This is strange, because the phenomenon definitely > is a new one. are you tracing the shell or the child? > > ktracing bash shows that no SIGCONT is ever sent to the foreground > job. This looks like a bash bug, although its sudden appearance > is mysterious. > > -- > Christian "naddy" Weisgerber naddy@mips.inka.de > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0208061828020.65715-100000>