Re: xemacs coredump in M-x eval-print-last-sexp

Jerry> No matter what the value of var is here, that shouldn't Jerry> happen. When it's a number, the first test should fail and Jerry> shortcut the second one ... shouldn't it? Yes, but it doesn't always. We've seen a crash where the compiler was doing gcse optimization (IIRC), and read ahead. This happened because the compiler convinced itself somehow that Lisp_Object was a pointer when it was actually holding a Lisp integer. However ... --use-union-type=yes made that one go away. According to Jeff Mincy (IIRC) this one doesn't. :-( I'll try to find the old crash; it was something that happened on one of {Unix,Cygwin,native Windows} but not on the others. 6--12 months ago, I think. One of the Russian guys was involved, maybe Nick Pakoulin. (Why can't I remember the damn bug!? Wetware!!) If anyone else cares to look.... -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py