Problem
When trying to rebuild the kernel, one of the following error messages is displayed:
UX:idmkunix: ERROR: Not enough memory for change tableORSegmentation Fault - core dumpedORBus Error - core dumpedand then the idbuild fails. Cause
It is possible that the file /etc/conf/cf.d/changedb has become corrupted.
Solution
First, rename the file to changedb.bak and then relink the kernel using /etc/conf/bin/idbuild with both the -B or -# options.
This removal of the changedb file should resolve the problem.
The "-#" option will generate verbose debug output, which may be of use if the relink still fails.
You can also run:# /etc/conf/bin/idcpunixto copy the unix kernel to /standand:# /etc/conf/bin/idmkenvto remake the kernel environment, usually done upon reboot.
NOTES: One of the /etc/conf/pack.d/<driver>/space.c files may include
a header file which does not exist on the system.Try running a "sar -r 1 1" to find out how much memory is actually available on the system should the problem be a true lack of memory.
In the case of a core dump, it is likely that the process which
dumped core is an instance of /etc/conf/bin/idmkunix, and that the
core file itself will be located in /etc/conf/cf.d. So if removing
the changedb file does not resolve the issue, try to verify whether
idmkunix was indeed the binary which caused the core dump. To do
this, you can use the debug(1) debugger; for example:# debug -ic core.23631
Error: Could not access idmkunix
debug>Here, "core.23631" is the core file, found in /etc/conf/cf.d; 23631 is the process ID of the process which dumped core. The error message immediately shows that it was "idmkunix" which dumped core. Thus in the case where removing changedb does not fix the problem, you can note what binary _did_ lead to the core dump, along with output generated by the "-#" option to idbuild, to hopefully obtain enough useful information to resolve the issue.