From: Kenichi Handa <handa@m17n.org>
To: "Johan Bockgård" <bojohan@gnu.org>
Cc: 9496@debbugs.gnu.org
Subject: bug#9496: 24.0.50; Segfault on TAB-only composition
Date: Fri, 11 Nov 2011 16:15:38 +0900 [thread overview]
Message-ID: <tl7obwj6sf9.fsf@m17n.org> (raw)
In-Reply-To: <8739g0tcp5.fsf@gnu.org> (message from Johan Bockgård on Tue, 13 Sep 2011 22:22:14 +0200)
In article <8739g0tcp5.fsf@gnu.org>, Johan Bockgård <bojohan@gnu.org> writes:
> (insert (compose-string "\t"))
> Program received signal SIGSEGV, Segmentation fault.
> 0x00000000004d45d4 in x_set_glyph_string_gc (s=0x7fffffffae80) at xterm.c:1061
> 1061 PREPARE_FACE_FOR_DISPLAY (s->f, s->face);
> (gdb) bt
> #0 0x00000000004d45d4 in x_set_glyph_string_gc (s=0x7fffffffae80)
> at xterm.c:1061
> #1 x_draw_glyph_string (s=0x7fffffffae80) at xterm.c:2683
> This problem is not new, but due to other changes it now makes
> `describe-char' (C-u C-x =) crash when executed on a tab character.
> 2011-09-13 Johan Bockgård <bojohan@gnu.org>
> * xdisp.c (fill_composite_glyph_string): Always set s->face, to
> avoid a crash.
Thank you. Although we have not yet decided what is the
right displaying of such a composition, I've just installed
your fix at least to avoid crash.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2011-11-11 7:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 20:22 bug#9496: 24.0.50; Segfault on TAB-only composition Johan Bockgård
2011-09-14 5:33 ` Eli Zaretskii
2011-09-14 12:57 ` Kenichi Handa
2011-09-14 13:07 ` Eli Zaretskii
2011-09-15 0:28 ` Kenichi Handa
2011-09-15 0:47 ` Stefan Monnier
2011-09-15 4:10 ` Kenichi Handa
2011-11-11 7:15 ` Kenichi Handa [this message]
2012-02-03 19:28 ` Paul Eggert
2012-02-03 21:22 ` Eli Zaretskii
2012-02-03 22:07 ` Paul Eggert
2012-02-04 6:58 ` Eli Zaretskii
2012-02-04 7:18 ` Paul Eggert
2012-02-04 8:14 ` Eli Zaretskii
2012-02-04 23:43 ` Paul Eggert
2012-02-05 16:36 ` Eli Zaretskii
2012-02-05 16:39 ` Paul Eggert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tl7obwj6sf9.fsf@m17n.org \
--to=handa@m17n.org \
--cc=9496@debbugs.gnu.org \
--cc=bojohan@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.