From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Description of problem:
When using the harddrive kickstart option, anaconda fails
install exited abnormally - received signal 11
In looking and testing at the code, it appears that some
variables are not initialized properly. For example, in
file hdinstall.c, function setKickstartHD, the addresses
of biospart, partition, and dir are passed to poptGetContext.
But it appears that if the corresponding option is not
selected in harddisk, then that variable is not updated,
yielding a segmentation violation later, when referenced.
Similar uninitialized variables appear to exist in
- setKickstartURL (char *url)
- useKickstartDD (char *src)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Whether it is reproducible depends on the state of memory previously
2. Attempt a harddisk install from a kickstart file, without setting
Actual Results: install exited abnormally - received signal 11
Expected Results: install should have succeeded
Fixed in CVS
Thanks for the quick update. I tested it with anaconda-10.0.3.8-1,
and it works.
But I did notice that in file driverdisk.c, function useKickstartDD,
src remains unitialized (as also listed in the bug description
above). Unlike in the harddrive case, a segmentation
violation can only occur if the syntax of the driverdisk is not
correct (missing args), so it's not as likely. But by simply
initializing src to NULL, anaconda would provide a descriptive warning
and proceed, instead of a signal 11 error message and crash.