Aaron Sloman <axs@cs.bham.ac.uk> wrote:
> 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.
> 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/
Perhaps I'm half-remembering some complaint about the Redhat patches?
Now that you mention it, I recall that I *have* seen complaints, but
I mostly use Mandrake (which was derived from Red Hat originally, but
the development forked a long time ago, I think) so didn't pay much
attention.
Just to narrow it down, do you know whether the saved image depended
on the system libraries (e.g. GNU math libraries)? If saved images
which were "pure" poplog (e.g. just manipulating lists etc.) also
caused segmentation faults, then ISTM less likely that it's anything
to do with C libraries loaded at runtime (i.e. .so files).
Or, to put it another way, have you experimented with creating
a small saved image on top of basepop11, and seeing if that works?
Jonathan
|