🚀 go-pugleaf

This is on emacs 18.55:

I had an emacs abort today when I had two big files loaded that just eat up
all memory. Apparently there wasn't even enough memory to display the
warning message. I can imagine emacs aborting then, but the abort was in
free() on a sanity check. So it might be a real bug somewhere. 

By the way I think it would be useful if the abort() calls would be
accompanied by some output on stderr.

Here is the traceback:

_free+0x30:	_abort	()
_make_gap+0x42:	_realloc(0x343928, 0x7F1)
_InsCStr+0x48:	_make_gap	(0x7F1)
_print+0x1B0:	_strout	(0x3A9B70, 0x21, 0x10A300C)
_Fprinc+0xF0:	_print	(0x33A9B6C, 0x10A300C, 0x0)
_malloc_warning_1+0xA:	_Fprinc	()
_malloc_warning+0x1C:	_internal_with_output_to_temp_buffer	(0x85264, 0x23BC4, 0x33A9B6C)
_malloc+0x4E:	_morecore	(0x4)
_Fmake_vector+0x50:	_malloc	(0x3C)
_Fcurrent_window_configuration+0xBA:	_Fmake_vector	(0xD, 0x10A300C)
_Fsave_window_excursion+0x22:	_Fcurrent_window_configuration	()
_Feval+0x560:	???	(0x307FE34, 0x40805C8, 0x12)
_Fprogn+0xEE:	_Feval	()
_funcall_lambda+0x1A2:	_Fprogn	()
_apply_lambda+0x100:	_funcall_lambda	(0x5080674, 0x1, 0xFFEFF318)
_Feval+0x642:	_apply_lambda	(0x5080674, 0x506C688, 0x1)
_Fprogn+0xEE:	_Feval	()
_funcall_lambda+0x1A2:	_Fprogn	()
_Ffuncall+0x4B2:_funcall_lambda	(0x506C698, 0x0, 0xFFEFF4D8)
_apply1+0x14:	_Ffuncall	(0x1, 0xFFEFF4D4)
_Fcommand_execute+0x124:_Fcall_interactively	(0x10BAD4C, 0x10A300C)
_command_loop_1+0x590:	_Fcommand_execute	(0x10BAD4C, 0x10A300C)
_internal_condition_case+0xAC:	???	()
_command_loop_2+0x14:	_internal_condition_case(0x10D3E, 0x10A30FC, 0x1097A)
_command_loop+0x54:	_internal_catch	(0x10A30E8, 0x10C36, 0x10A300C)
_main+0x4AA:	_Frecursive_edit()
__start+0x6E:	_main	(0x5, 0xFFEFFA74)
-- 
Piet* van Oostrum, Dept of Computer Science, Utrecht University,
Padualaan 14, P.O. Box 80.089, 3508 TB Utrecht, The Netherlands.
Telephone: +31 30 531806   Uucp:   uunet!mcsun!ruuinf!piet
Telefax:   +31 30 513791   Internet:  piet@cs.ruu.nl   (*`Pete')