From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 36166@debbugs.gnu.org
Subject: bug#36166: 27.0.50; Crash visiting HELLO when fringe-mode is disabled
Date: Tue, 11 Jun 2019 17:26:57 +0300 [thread overview]
Message-ID: <83ftog9ozy.fsf@gnu.org> (raw)
In-Reply-To: <m2k1dsy1tu.fsf@gmail.com> (message from Robert Pluim on Tue, 11 Jun 2019 10:15:57 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Date: Tue, 11 Jun 2019 10:15:57 +0200
>
>
> HOME=/tmp src/emacs /tmp/HELLO
>
> where /tmp/.emacs.d/init.el contains:
>
> (custom-set-variables
> '(fringe-mode 0 nil (fringe))
> )
>
> and /tmp/HELLO is etc/HELLO with all the non-ASCII removed except for
> the line in Maldivian. I donʼt have a font that can display Maldivian.
>
> gdb:
>
> Thread 3 received signal SIGSEGV, Segmentation fault.
> ns_compute_glyph_string_overhangs (s=0x7ffeefbfc7e0) at nsterm.m:2941
> 2941 if (EQ (font->driver->type, Qns))
> (gdb) bt
> #0 ns_compute_glyph_string_overhangs (s=0x7ffeefbfc7e0) at nsterm.m:2941
> #1 0x0000000100039d74 in draw_glyphs (w=<optimized out>, x=562, row=0x1050c5b00, area=TEXT_AREA, start=0, end=50,
> hl=DRAW_NORMAL_TEXT, overlaps=0) at xdisp.c:27050
This appears to be NS-specific: the NS version of the
compute_glyph_string_overhangs method is very different from the X and
w32 versions, and lacks some safety devices. (I did try the recipe on
w32, and didn't see any crashes.)
Thanks.
next prev parent reply other threads:[~2019-06-11 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 8:15 bug#36166: 27.0.50; Crash visiting HELLO when fringe-mode is disabled Robert Pluim
2019-06-11 14:26 ` Eli Zaretskii [this message]
2019-06-11 14:51 ` Robert Pluim
2019-06-11 14:59 ` Eli Zaretskii
2019-06-11 15:17 ` Robert Pluim
2019-06-11 15:26 ` Eli Zaretskii
2019-06-11 15:32 ` Robert Pluim
2019-06-11 15:53 ` Eli Zaretskii
2022-01-29 14:52 ` Lars Ingebrigtsen
2022-01-30 15:01 ` Robert Pluim
2022-01-30 16:09 ` Lars Ingebrigtsen
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=83ftog9ozy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36166@debbugs.gnu.org \
--cc=rpluim@gmail.com \
/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).