I occasionally get "Out of memory" errors, and then I get an infinite
loop of "report error is buggy" errors. First of all, I'm tired of
that message - it should probably read "error occurred during error
processing!" or something. I'm also tired of the infinite loop, which
the doc says err_counter is supposed to prevent. However, even if
err_counter is greater than one it calls STk_show_eval_stack(5), which
produces the error again.
What I would really like is to find out where the error really
happened. If STk_show_eval_stack didn't cons it might be possible.
It calls STk_print and STk_uncode. STk_print looks ok, but STk_uncode
does lots of consing. Maybe if err_counter is nonzero
STk_show_eval_stack could avoid doing a full uncode, just print
something that might give a clue what's going on...
--
David Fox http://found.cs.nyu.edu/fox xoF divaD
NYU Media Research Lab fox_at_cs.nyu.edu baL hcraeseR aideM UYN
Received on Thu Oct 03 1996 - 20:38:31 CEST