Daniel Novotny writes:
execute_optimized_program () - it all was in my bugreport ZIP file,
I sent with the previous mail (the text file xemacs-vi-mode-bugreport.txt
shows my GDB session, with me going up and down the stack and
Sorry, but my mailreader doesn't handle zip files automatically. You
could wait for me to save and open the zip file manually, but that
will take a while, maybe forever if your mail ends up far enough down
Or you can take what hints I can give in 60 seconds, and maybe
somebody else will pick up the ball during the conversation. That's
just the reality of my life for the next month.
> If it's a compiler issue, it may have to do with misuse of
> variables. You could try compiling without the register declaration.
Interesting, when I comment out the register declaration specifier
on all the variables, I am getting another error elsewhere in the code:
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.
XEmacs-Beta mailing list