----- "Stephen J. Turnbull" <stephen(a)xemacs.org> wrote:
Daniel Novotny writes:
> > If it's a compiler issue, it may have to do with misuse of
> > variables. You could try compiling without the register
> Interesting, when I comment out the register declaration specifier
> on all the variables, I am getting another error elsewhere in the
> 100% reproducible the same thing again, a segfault
> I attach the "where" backtrace in this mail
That backtrace is partial, and just shows XEmacs trying to print out
an error it encountered inside the error handler. This is hard to
avoid since XEmacs is known to be in a bad state when it hits an
internal error (AKA "impossible" condition).
We need to see the whole backtrace.
OK, I didn't realize that, attaching the whole backtrace
XEmacs-Beta mailing list