[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


GC-OVERFLOW  isn't really supposed to be an error, which is why there is
no errframe.  GC-LOSSAGE is supposed to be an error, with an errframe,
but sometimes facilities are so cramped that the only thing possible
is to print out a message and punt back to toplevel.  What kind of
message was being printed out by GC-OVERFLOW that made you think it
was a standard error message?