From owner-freebsd-bugs@FreeBSD.ORG Thu Jan 9 10:50:01 2014 Return-Path: Delivered-To: freebsd-bugs@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 7EC2972D for ; Thu, 9 Jan 2014 10: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 6B85A165B for ; Thu, 9 Jan 2014 10: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 s09Ao1lp090417 for ; Thu, 9 Jan 2014 10: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 s09Ao1Cg090416; Thu, 9 Jan 2014 10:50:01 GMT (envelope-from gnats) Date: Thu, 9 Jan 2014 10:50:01 GMT Message-Id: <201401091050.s09Ao1Cg090416@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Alexander Yerenkow Subject: Re: gnu/185603: csh eats memory X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Alexander Yerenkow List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jan 2014 10:50:01 -0000 The following reply was made to PR gnu/185603; it has been noted by GNATS. From: Alexander Yerenkow To: freebsd-bug-followup , Alexander Yerenkow Cc: Subject: Re: gnu/185603: csh eats memory Date: Thu, 9 Jan 2014 12:46:48 +0200 --047d7b673c5e90288004ef875300 Content-Type: text/plain; charset=ISO-8859-1 Seems corrupted history was culprit https://access.redhat.com/site/solutions/41146 I'd suggest to not parse whole history if it's corrupted, and warn user (maybe). -- Regards, Alexander Yerenkow --047d7b673c5e90288004ef875300 Content-Type: text/html; charset=ISO-8859-1
Seems corrupted history was culprit


I'd suggest to not parse whole history if it's corrupted, and warn user (maybe).

--
Regards,
Alexander Yerenkow
--047d7b673c5e90288004ef875300--