From owner-freebsd-current@FreeBSD.ORG Thu Apr 29 21:41:46 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9D65F106566C for ; Thu, 29 Apr 2010 21:41:46 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [109.74.192.160]) by mx1.freebsd.org (Postfix) with ESMTP id 5D7C58FC0C for ; Thu, 29 Apr 2010 21:41:46 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id CA0CBC400D; Thu, 29 Apr 2010 21:41:44 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on muon.cran.org.uk X-Spam-Level: X-Spam-Status: No, score=-2.3 required=8.0 tests=AWL,BAYES_00,RDNS_DYNAMIC autolearn=no version=3.2.5 Received: from core.draftnet (87-194-158-129.bethere.co.uk [87.194.158.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Thu, 29 Apr 2010 21:41:44 +0000 (UTC) From: Bruce Cran To: freebsd-current@freebsd.org Date: Thu, 29 Apr 2010 22:41:30 +0100 User-Agent: KMail/1.13.2 (FreeBSD/9.0-CURRENT; KDE/4.4.2; amd64; ; ) References: <20100429153154.GA70173@darkthrone.kvedulv.de> <20100429211256.GA73377@darkthrone.kvedulv.de> <4BD9F7F1.7020607@icyb.net.ua> In-Reply-To: <4BD9F7F1.7020607@icyb.net.ua> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201004292241.30915.bruce@cran.org.uk> Cc: Michael Moll , Andriy Gapon Subject: Re: config(8) dumps core X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Apr 2010 21:41:46 -0000 On Thursday 29 April 2010 22:19:45 Andriy Gapon wrote: > on 30/04/2010 00:12 Michael Moll said the following: > > Hi, > > > > On Thu, Apr 29, 2010 at 11:33:30PM +0300, Andriy Gapon wrote: > >> on 29/04/2010 18:31 Michael Moll said the following: > >> You can use hd to see if you indeed have '\0' (0x00) symbol somewhere > >> within your kernel config file. > > > > Thanks, I checked this and there are no 0x00s in the config file itself, > > Then that assert message is strange. > Or there is something else to this situation. > > > but a hd to /boot/kernel/kernel reveals: > > > > 09 66 77 69 70 0a 64 65 76 69 63 65 09 64 63 6f |.fwip.device.dco| > > 6e 73 0a 64 65 76 69 63 65 09 64 63 6f 6e 73 5f |ns.device.dcons_| > > 63 72 6f 6d 0a 00 00 00 00 00 00 00 00 00 00 00 |crom............| > > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| > > > > This also explains why a recent config-binary worked against the old > > kernel... The were some commits to /src/usr.sbin/config/* in the last > > weeks, maybe one of them broke this. > > Actually I think that this doesn't mean anything. > /boot/kernel/kernel is a binary, an executable, it is expected to have a > fair amount of 0x00 in it. > That assert was specifically about kernel _config_ file. It's expected to have some 0x00s, but hopefully not in the middle of the embedded kernel configuration file that has recently been added to GENERIC :) -- Bruce