From owner-freebsd-current@FreeBSD.ORG  Thu Apr 29 21:19:49 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 6887D106564A
	for <freebsd-current@freebsd.org>; Thu, 29 Apr 2010 21:19:49 +0000 (UTC)
	(envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id AB1F88FC0A
	for <freebsd-current@freebsd.org>; Thu, 29 Apr 2010 21:19:48 +0000 (UTC)
Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua
	[212.40.38.100])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA18333;
	Fri, 30 Apr 2010 00:19:45 +0300 (EEST)
	(envelope-from avg@icyb.net.ua)
Received: from localhost.topspin.kiev.ua ([127.0.0.1])
	by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
	id 1O7b97-0009jt-Me; Fri, 30 Apr 2010 00:19:45 +0300
Message-ID: <4BD9F7F1.7020607@icyb.net.ua>
Date: Fri, 30 Apr 2010 00:19:45 +0300
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Thunderbird 2.0.0.24 (X11/20100321)
MIME-Version: 1.0
To: Michael Moll <kvedulv@kvedulv.de>
References: <20100429153154.GA70173@darkthrone.kvedulv.de>
	<4BD9ED1A.3050100@icyb.net.ua>
	<20100429211256.GA73377@darkthrone.kvedulv.de>
In-Reply-To: <20100429211256.GA73377@darkthrone.kvedulv.de>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Apr 2010 21:19:49 -0000

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.


-- 
Andriy Gapon