On Fri, 2002-01-04 at 12:39, Sean Neakums wrote:
> I think I can finally reproduce the bogus dumps. I just did it here,
> three times. What I did was: run the io-test program above on two
> different files for approx three minutes, then start the emacs dump.
> When the dump completed, I started a third io-test and left the three
> of them run for about five or so more minutes. What I'm trying to do
> with all this I/O is to force the dumped binary's pages to be written
> to disk.
Can you expand on the 'dumps' I am not really familiar with the
emacs build process, so I don't know which part of the process
you are refering to here.
> So after the five minutes or so, I killed the io-test threads and
> attempted to start the dumped binary, which failed with a `cannot
> execute' message from the shell. I looked in the file, and it pure
> garbage: not even an "ELF" string at the start of the file.
> I am now going to do a build of the upstream source and see if I can
> make the dump break on that too. I'm hopeful that it will, as the
> unexec code is the same in upstream as in the Debian emacs21 package.
> ///////////////// | | The spark of a pin
> <sneakums@xxxxxxxx> | (require 'gnu) | dropping, falling feather-like.
> \\\\\\\\\\\\\\\\\ | | There is too much noise.
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@xxxxxxx