>>>> "David" == David Bush
David> Dear Bug Team!
David> I've gotten two segmentation violations in the garbage collector. It
David> appears to be the result of an infinite recursion in the mark phase.
David> The stack trace is from the first occurence in an XEmacs that had been
David> running for a few days doing language editing plus running VM. The
David> second occured within a few minutes. All that had happened was an
David> edit of a text file, a few file insertions, a few pastes from the
David> clipboard plus starting VM. The crash happened while VM was
David> processing an HTML formatted message.
David> This is updated from CVS on Friday morning.
David> It isn't possible to get a Lisp backtrace
David> This is an edited version of the stack trace showing the top and
David> bottom ot the trace. The pattern at the top of the stack repeats for
David> about 19000 frames and then switches to the pattern shown in the other
David> section of the trace.
Hm, to me this doesn't look like infinite recursion: I don't see any
duplicate Lisp objects along the way. I suspect this is simply a
stack overflow. It's certainly likely that the current, temporary
kkcc marker consumes more stack than the old one. (The plan is to
replace it by one that doesn't use any stack at all.)
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla