From owner-freebsd-stable@FreeBSD.ORG Thu Jul 4 13:09:06 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 81407E68 for ; Thu, 4 Jul 2013 13:09:06 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id 467AD1482 for ; Thu, 4 Jul 2013 13:09:06 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::199c:6fe6:9d79:6781] (unknown [IPv6:2001:7b8:3a7:0:199c:6fe6:9d79:6781]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id C03A75C43; Thu, 4 Jul 2013 15:08:57 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: Phantom nulls in usbdevs.h during 9-STABLE kernel build From: Dimitry Andric In-Reply-To: Date: Thu, 4 Jul 2013 15:08:57 +0200 Content-Transfer-Encoding: 7bit Message-Id: <2D61560D-E3D9-4558-8715-8215DBBF21D9@FreeBSD.org> References: To: J David X-Mailer: Apple Mail (2.1508) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jul 2013 13:09:06 -0000 On Jul 4, 2013, at 04:43, J David wrote: > We are seeing strange problems building the kernel on 9-STABLE. The > problem is intermittent and will go away if we build enough times in a row > without making any changes. > > > The problem seems to be that the usbdevs.h file (which appears to be > automatically generated) gets random NULL bytes in it. ... > On the second failure posted below I took a hex dump of the usbdevs.h file. > I don't see any NULLs at the target location, which is an empty line. > (Just 0a 0a for the empty line.) In fact there are no nulls anywhere in > the file. So the actual file does *not* have any NUL characters in it? What happens if you run e.g. sha1(1) over it a million times? If there are NUL characters, there might be a bug in the awk script that generates usbdevs.h. If there are no NUL characters, and you get a random failure each time, there might be a bug in clang. But did you mean you also saw it with gcc? -Dimitry