can --enable-dump-in-exec be used with 'mc-alloc'?

[Marcus Crestani]

>>>>>"MF" == Mike FABIAN <mfabian at suse.de> writes:
MF> Is there a specific reason why is it not enabled by default when
MF> using 'mc-alloc'?

With `mc-alloc', the dumped data is not used directly out of the dump
file; each dumped object is handed to the allocator.  Therefore, the
dump image has only to be present in memory while restoring the dumped
objects, which is done immediately after XEmacs is launched.  After
that, the memory of the dump image can be freed.

If the dump image is written into the executable, this memory cannot
be freed, and thus the dumped objects are using twice their size in
memory (in the dump image and allocated with the new allocator).

If the dump image is written into a separate file, this memory can be
freed after loading the objects.  The size of the dump image depends
on your configuration and is approximately 5 MB.

With this configuration option, the user has the choice: separate file
vs. memory wastage.

MF> Is that default meant as a recommendation not to enable it when
MF> using 'mc-alloc'?

Yes, assuming the user wants to save memory.

-- 
Marcus