unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-pretest-bug@gnu.org
Subject: bug#1105: Looping in redisplay due to font problem
Date: Tue, 07 Oct 2008 20:26:01 +0900	[thread overview]
Message-ID: <E1KnAhV-0007aZ-Vn@etlken.m17n.org> (raw)
In-Reply-To: <87y711r87e.fsf@cyd.mit.edu> (message from Chong Yidong on Mon, 06 Oct 2008 12:37:09 -0400)

In article <87y711r87e.fsf@cyd.mit.edu>, Chong Yidong <cyd@stupidchicken.com> writes:

> Yes, it always seems to stop at this place.  Here's `bt full' and a
> debugging session.  I don't see anything wrong OTOH, and am unsure about
> what to look for.  Stepping forward in gdb doesn't work because the
> program is stopped inside `select'.  Any suggestions?

> #0  0x00007f6dd0fe5433 in select () from /lib/libc.so.6
> #1  0x00007f6dcf0422b6 in ?? () from /usr/lib/libxcb.so.1
> #2  0x00007f6dcf0428eb in ?? () from /usr/lib/libxcb.so.1
> #3  0x00007f6dcf043050 in xcb_send_request () from /usr/lib/libxcb.so.1
> #4  0x00007f6dd1943f1a in _XPutXCBBuffer () from /usr/lib/libX11.so.6
> #5  0x00007f6dd1944267 in ?? () from /usr/lib/libX11.so.6
> #6  0x00007f6dd19370bd in XSetClipMask () from /usr/lib/libX11.so.6
> #7  0x00000000004e426d in x_draw_glyph_string (s=0x7fffdd7a95e0)
>     at xterm.c:2883
>         relief_drawn_p = 0
> #8  0x00000000004617cc in draw_glyphs (w=0x1cd5ad0, x=72, row=0x1f727d0, 
>     area=TEXT_AREA, start=7, end=8, hl=DRAW_NORMAL_TEXT, overlaps=0)
>     at xdisp.c:20504

Please try to comment out all calls of XSetClipMask in
x_draw_glyph_string, and check if Emacs loops in redisplay.

---
Kenichi Handa
handa@ni.aist.go.jp






  reply	other threads:[~2008-10-07 11:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <873aj5lnt2.fsf@cyd.mit.edu>
2008-10-02 23:47 ` bug#1070: Looping in redisplay due to font problem Chong Yidong
2008-10-03  1:24   ` bug#1071: " Kenichi Handa
2008-10-03 16:18     ` bug#1076: " Chong Yidong
2008-10-06  2:32       ` bug#1097: " Kenichi Handa
2008-10-06 16:37         ` bug#1101: " Chong Yidong
2008-10-07 11:26           ` Kenichi Handa [this message]
2008-10-07 16:14             ` bug#1070: " Chong Yidong
2008-10-08  1:16               ` Kenichi Handa
2008-10-08 15:50                 ` Chong Yidong
2008-10-09 16:50             ` bug#1105: marked as done (Looping in redisplay due to font problem) Emacs bug Tracking System
2008-10-09 16:50           ` bug#1101: " Emacs bug Tracking System
2008-10-09 16:50         ` bug#1097: " Emacs bug Tracking System
2008-10-09 16:50       ` bug#1076: " Emacs bug Tracking System
2008-10-09 16:50     ` bug#1071: " Emacs bug Tracking System
2008-10-09 16:50   ` bug#1070: " Emacs bug Tracking System

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1KnAhV-0007aZ-Vn@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=1105@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-pretest-bug@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).