From owner-freebsd-current  Tue Aug  6 18:40:19 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6949537B401
	for <freebsd-current@freebsd.org>; Tue,  6 Aug 2002 18:40:15 -0700 (PDT)
Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F137943E65
	for <freebsd-current@freebsd.org>; Tue,  6 Aug 2002 18:40:13 -0700 (PDT)
	(envelope-from julian@elischer.org)
Received: from InterJet.elischer.org ([12.232.206.8])
          by sccrmhc02.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020807014010.BRYG221.sccrmhc02.attbi.com@InterJet.elischer.org>;
          Wed, 7 Aug 2002 01:40:10 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA71546;
	Tue, 6 Aug 2002 18:28:58 -0700 (PDT)
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?
In-Reply-To: <aipjlf$51b$1@kemoauc.mips.inka.de>
Message-ID: <Pine.BSF.4.21.0208061828020.65715-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG



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