Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Apr 2010 00:19:45 +0300
From:      Andriy Gapon <avg@icyb.net.ua>
To:        Michael Moll <kvedulv@kvedulv.de>
Cc:        freebsd-current@freebsd.org
Subject:   Re: config(8) dumps core
Message-ID:  <4BD9F7F1.7020607@icyb.net.ua>
In-Reply-To: <20100429211256.GA73377@darkthrone.kvedulv.de>
References:  <20100429153154.GA70173@darkthrone.kvedulv.de> <4BD9ED1A.3050100@icyb.net.ua> <20100429211256.GA73377@darkthrone.kvedulv.de>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BD9F7F1.7020607>