[Kaarthik Sivakumar] "Dump file too big for available space"
Stephen J. Turnbull
stephen at xemacs.org
Tue May 25 00:20:37 EDT 2004
>>>>> "Kaarthik" == Kaarthik Sivakumar <kaarthik at comcast.net> writes:
Kaarthik> I sent this mail last night, but it hasnt shown up yet
Kaarthik> on the mailing list. Maybe it got spam-blocked?
No. The list's procmail.log shows that it was sent out to Mailman,
Mailman's post log says soemthing from you went out to xemacs-beta a
couple minutes later; I assume it's the same thing. Unfortunately, I
don't have the necessary privilege to read the old mail logs, so I
can't say what happened with sendmail.
Kaarthik> What space is it talking about? Hard drive, stack,
Kaarthik> memory? Also what is the unit of space in the above,
Kaarthik> 2441380 MB, GB or bytes? Ok, not GB, definitely, and
Kaarthik> bytes hopefully.
It's bytes, and it's probably the size of the memory block to be
malloc'd and then filled with the dumped data.
Kaarthik> It seems to me like it expects each attempt at
Kaarthik> compilation would result in dumping an xemacs that has a
Kaarthik> size equal to (or smaller than) what the previous
Kaarthik> compile produced.
It's just an estimate, and for me when I get that "too small" error I
see the dump process redone automatically. So there is a another
problem manifesting in your build, and we need to find out what it is.
The fact that "make distclean" doesn't remove it is a bug. I'm not
sure where in the clean hierarchy that should be done, but I'll put it
in make distclean for now.
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
More information about the XEmacs-Beta