From owner-freebsd-current@FreeBSD.ORG  Mon Jan  3 19:07:30 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 2083716A4CE; Mon,  3 Jan 2005 19:07:30 +0000 (GMT)
Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5A8B143D39; Mon,  3 Jan 2005 19:07:29 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from elischer.org (julian.vicor-nb.com [208.206.78.97])
	by mail.vicor-nb.com (Postfix) with ESMTP
	id 278907A425; Mon,  3 Jan 2005 11:07:27 -0800 (PST)
Message-ID: <41D997EF.50809@elischer.org>
Date: Mon, 03 Jan 2005 11:07:27 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516
X-Accept-Language: en, hu
MIME-Version: 1.0
To: Scott Long <scottl@freebsd.org>
References: <21760.1104759281@critter.freebsd.dk>
	<41D9800C.8060202@freebsd.org>
In-Reply-To: <41D9800C.8060202@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: Poul-Henning Kamp <phk@phk.freebsd.dk>
cc: current@freebsd.org
Subject: Re: SIGSTOP/SIGCONT problem ? (scheduler or make(1) ?)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jan 2005 19:07:30 -0000



Scott Long wrote:

>>
>
> I've had problems recently with SIGSTOP not being honored while
> compiling files.  Probably what happened here is that gcc continued
> on its merry way and exited when it was done compiling gencodes.o.
> Unfortunately I don't have much more debugging information to offer 


I've seen this but only with make.