[Kaarthik Sivakumar] "Dump file too big for available space"
kaarthik at comcast.net
Wed May 26 07:09:49 EDT 2004
>>> "SJT" == Stephen J Turnbull <stephen at xemacs.org> writes:
Kaarthik> What space is it talking about? Hard drive, stack, memory?
Kaarthik> Also what is the unit of space in the above, 2441380 MB, GB
Kaarthik> or bytes? Ok, not GB, definitely, and bytes hopefully.
SJT> It's bytes, and it's probably the size of the memory block to be
SJT> malloc'd and then filled with the dumped data.
Maybe a hint in the message would be good, but then if it is meant to
correct itself, then there is no point in that.
Kaarthik> It seems to me like it expects each attempt at compilation
Kaarthik> would result in dumping an xemacs that has a size equal to
Kaarthik> (or smaller than) what the previous compile produced.
SJT> It's just an estimate, and for me when I get that "too small"
SJT> error I see the dump process redone automatically. So there is a
SJT> another problem manifesting in your build, and we need to find
SJT> out what it is.
I have an output from 'script' of the make failure. And I can
reproduce it at will anyways. So how do you want to work on this? Can
you show me an output from make that shows what happens in your case?
SJT> The fact that "make distclean" doesn't remove it is a bug. I'm
SJT> not sure where in the clean hierarchy that should be done, but
SJT> I'll put it in make distclean for now.
More information about the XEmacs-Beta