Re: XEmacs kills X server, receives life sentence

Jerry> I just discovered that looking at lisp/paragraphs.el is Jerry> sufficient to trigger the X server crash. That is very bad. Jerry> What fun! Does anybody know what 21.5 is doing differently Jerry> from 21.4 that might help track down this bug? My guess is that it is actually calling XDrawImageString16, while 21.4 does not because it doesn't have the required font. Perhaps XDrawImageString16 is using an inappropriate font (eg, a font for ISO-8859-1 only). If not, I would guess that what is happening is that your XEmacs is configured to use broken fonts. Either way, XEmacs is sending requests to display glyphs that don't exist, the server accesses past the end of the array, X code of course does no bounds checking (RealMen[tm] don't even check for NULL pointers, you know), whammer jammer, momma, we goin' down! "OBJECTION!! Your honor, that was a Conclusion By The Witness!" Sustained ... but I agree. ;-) Proscution-witness-judge-jury-AND-hangman-ly y'rs, -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN I am an XEmacs developer because X11 doesn't check for NULL pointers.