- the backtraces show that some kind of signal thingy happens at
alloc.c:4244, but that line is just a function call and I can't see how it
can fail. Please keep an eye on this. Try to see why it crashed at that
point.
Various optimizations such as cross-jumping can confuse the line
number. I think that inlining can also cause problems to be referred
to the wrong line. Back when I worked on GCC, to debug a possible GCC
optimization bug once I knew which function was miscompiled, I would
just compare the .s output with the source.
I suggest testing with the latest GCC before going to so much trouble.
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
