From owner-freebsd-stable@FreeBSD.ORG Wed Sep 14 21:01:32 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A275A1065677; Wed, 14 Sep 2011 21:01:32 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from mail.ciam.ru (mail.ciam.ru [91.209.218.18]) by mx1.freebsd.org (Postfix) with ESMTP id 4B9318FC19; Wed, 14 Sep 2011 21:01:32 +0000 (UTC) Received: from [46.242.19.18] (helo=[172.16.100.20]) by mail.ciam.ru with esmtpa (Exim 4.x) id 1R3wFr-000Ifq-Sd; Thu, 15 Sep 2011 00:40:24 +0400 Message-ID: <4E711137.2080305@FreeBSD.org> Date: Thu, 15 Sep 2011 00:40:23 +0400 From: Sergey Matveychuk User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13 MIME-Version: 1.0 To: Dmitry Morozovsky References: <201109121458.15661.jhb@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: lulf@freebsd.org, freebsd-stable@freebsd.org Subject: Re: csup crash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2011 21:01:32 -0000 13.09.2011 03:29, Dmitry Morozovsky wrote: > On Mon, 12 Sep 2011, John Baldwin wrote: > >> On Monday, September 12, 2011 2:01:16 am Dmitry Morozovsky wrote: >>> Dear colleagues, >>> >>> I found csup is crashing on my building machine on some broken repo element, >>> but cannot quickli realize what's the source of problem >> >> What OS version are you running? I wonder if you have this fix: > > it is on rather fresh stable/8: > > FreeBSD beaver.rinet.ru 8.2-STABLE FreeBSD 8.2-STABLE #5 r224908M: Tue Aug 16 > 15:43:23 MSD 2011 marck@beaver.rinet.ru:/usr/obj/usr/src/sys/BEAVER amd64 > > so I suppose I'd have the fix you'd mentioned. > > I'm still have broken repo as a ZFS snapshot, so I'm ready to provide more > info or test any fix you provide. > Have you found a broken file? What its content?