config(8) dumps core

[Bruce Cran]

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