From owner-freebsd-arm@FreeBSD.ORG Wed Nov 20 00:50:01 2013 Return-Path: Delivered-To: freebsd-arm@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A2F4A390 for ; Wed, 20 Nov 2013 00:50:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 913242A0E for ; Wed, 20 Nov 2013 00:50:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rAK0o19b067575 for ; Wed, 20 Nov 2013 00:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rAK0o0SQ067560; Wed, 20 Nov 2013 00:50:00 GMT (envelope-from gnats) Date: Wed, 20 Nov 2013 00:50:00 GMT Message-Id: <201311200050.rAK0o0SQ067560@freefall.freebsd.org> To: freebsd-arm@FreeBSD.org Cc: From: Howard Su Subject: Re: arm/183926: Crash when ctrl-c while process is enter X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: Howard Su List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Nov 2013 00:50:01 -0000 The following reply was made to PR arm/183926; it has been noted by GNATS. From: Howard Su To: bug-followup@freebsd.org Cc: Subject: Re: arm/183926: Crash when ctrl-c while process is enter Date: Wed, 20 Nov 2013 08:42:24 +0800 --001a11343d08fbe31b04eb910db8 Content-Type: text/plain; charset=ISO-8859-1 it was an artifact of experimental code. This is confirmed by me and Ian@so that this is not able to reproduce in stock kernel. -- -Howard --001a11343d08fbe31b04eb910db8 Content-Type: text/html; charset=ISO-8859-1 it was an artifact of experimental code. This is confirmed by me and Ian@ so that this is not able to reproduce in stock kernel.

--
-Howard
--001a11343d08fbe31b04eb910db8--