Re: Segv running tty gnuclient under an x gnuserv

Robert Pluim <rpluim(a)bigfoot.com&gt; writes: Sounds logical, as this was a major rewrite the of the text glyph code 2000-04-02 IKEYAMA Tomonori <tomonori(a)suiyokai.org&gt; * redisplay.c (add_glyph_rune): Don't set 0 to bufpos for text image glyph if allow_cursor. (add_hscroll_rune): Don't allow cursor to border glyph. (create_text_block): Ditto. * redisplay-output.c (redisplay_move_cursor): Do nothing even if text not in buffer. (redisplay_output_layout): Call ensure_face_cachel_complete for text image glyph. 2000-03-16 IKEYAMA Tomonori <tomonori(a)suiyokai.org&gt; * redisplay.c (add_glyph_rune): Adding text image as text runes. * redisplay-output.c (redisplay_move_cursor): NO_CURSOR if text not in buffer * redisplay-tty.c (tty_output_display_block): Delete the routine for text image glyph * redisplay-x.c (x_output_display_block): ditto * redisplay-msw.c (mswindows_output_display_block): ditto What thi patch did was that instead of using special cased stuff do do display text glyphs, it returns back to the normal textoutput routines. That removes a lot of extra code and as a side effect makes text glyphs mule-aware. Unfortunately I cannot reproduce the crash (although I was lazy and used 'xemacs -q -f gnuserv-start -f display-time instead). For me tty frame comes up with "/path/to/xpm/image/for/clock/digit.xpm" in the modeline and then at the next refresh becomes text. (If I switch focus back to the X frame it changes back to graphics. It seems to me that displaytime is using glyphs in the wrong way. Still XEmacs should not crash). What wonders me is which of the two texts causes the crash. I'll have another look at the change. No, their mine as well! :-) Jan