I wrote:
[JLC]
> > Poplog saved images depend crucially on the base they are
> > being loaded into being the same as the one they were
> > compiled under, so if any parts of that base are loaded into a
> > different part of the address space, you'd get segmentation
> > faults ...
>
> This sounds like a plausible explanation but for one problem: if I
> get a new kernel (even the latest stable one: 2.6.15.1) and compile
> it myself, I don't have the problem.
>
> So recent kernel features are not enough to cause the problem.
>
> If I get a pre-built kernel later than 2.6.11-something I get the
> problem.
>
> Is it possible that some ways of compiling the kernel produce that
> effect which is not turned on by default in the kernel sources, but
> is turned on in new pre-built Fedora Core 3 and 4 kernels?
>
> I could try searching through the config files which determine what
> goes in to the kernel when it is compiled, but linux kernel config
> files are huge: there are so many options that I fear I would not
> even recognise the one that's relevant, if there is one.
I have just talked to someone who teaches operating systems here
and who knows a lot more than I do about linux. He said that when
I get a pre-built kernel for Fedora Core 3, or 4 it will include
a lot of patches put in by Redhat which is not in the core kernel
sources. So it may be that the segmentation fault errors when
starting up a saved image are a result of additions to the kernel
inserted by RedHat. Maybe one day I shall find time to check that
by getting the sources for FC and compiling those. For now when
I compile a kernel it's a pure kernel from
http://www.kernel.org/
Aaron
http://www.cs.bham.ac.uk/~axs/
|