From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22818@debbugs.gnu.org, josh@berdine.net
Subject: bug#22818: 25.1.1 Emacs.app crash ns_compute_glyph_string_overhangs
Date: Sat, 19 Nov 2016 11:18:23 +0000 [thread overview]
Message-ID: <20161119111823.GA66770@breton.holly.idiocy.org> (raw)
In-Reply-To: <83k2bzbw8g.fsf@gnu.org>
On Sat, Nov 19, 2016 at 12:27:27PM +0200, Eli Zaretskii wrote:
> So the question now becomes: how did that glyph_string got a NULL
> font? The answer is somewhere in the code that generates glyph
> strings as part of the call to BUILD_GLYPH_STRINGS. Can you try
> figuring out why does that happen, by stepping through the code in
> BUILD_GLYPH_STRINGS?
I’m trying to work out how to do this, but in the mean‐time here’s s->face:
(lldb) fr v *s->face
(face) *s->face = {
lface = {
[0] = 17952
[1] = 4311871236
[2] = 4298401388
[3] = 32304
[4] = 482
[5] = 32304
[6] = 32304
[7] = 0
[8] = 0
[9] = 4313454388
[10] = 4313454420
[11] = 0
[12] = 0
[13] = 0
[14] = 0
[15] = 4356698701
[16] = 0
[17] = 4313448132
[18] = 44496
}
id = 19
gc = 0x0000000000000000
stipple = 0
foreground = 2
background = 1
underline_color = 0
overline_color = 0
strike_through_color = 0
box_color = 0
font = 0x0000000000000000
fontset = 3
box_line_width = 0
box = FACE_NO_BOX
underline_type = FACE_UNDER_LINE
use_box_color_for_shadows_p = false
underline_p = false
overline_p = false
strike_through_p = false
foreground_defaulted_p = false
background_defaulted_p = false
underline_defaulted_p = false
overline_color_defaulted_p = false
strike_through_color_defaulted_p = false
box_color_defaulted_p = false
tty_bold_p = false
tty_italic_p = false
tty_underline_p = false
tty_reverse_p = false
colors_copied_bitwise_p = true
overstrike = false
synth_ital = false
hash = 7029
next = 0x000000010fd7e5d0
prev = 0x000000010c5eda00
ascii_face = 0x00000001011afac0
}
I don’t know if that tells you anything useful.
--
Alan Third
next prev parent reply other threads:[~2016-11-19 11:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 13:41 bug#22818: 25.0.91; nextstep/Emacs.app Crash ns_compute_glyph_string_overhangs Aaron S. Hawley
2016-05-18 20:07 ` Alan Third
2016-05-18 21:09 ` Aaron S. Hawley
2016-11-18 21:31 ` bug#22818: 25.1.1 Emacs.app crash ns_compute_glyph_string_overhangs Josh Berdine
2016-11-19 7:07 ` Eli Zaretskii
2016-11-19 10:07 ` Alan Third
2016-11-19 10:27 ` Eli Zaretskii
2016-11-19 11:18 ` Alan Third [this message]
2016-11-19 11:43 ` Eli Zaretskii
2016-11-19 14:53 ` Alan Third
2016-11-19 15:09 ` Eli Zaretskii
2016-11-19 15:51 ` Alan Third
2016-11-19 18:12 ` Eli Zaretskii
2016-11-19 19:05 ` Alan Third
2016-11-19 19:27 ` Eli Zaretskii
2016-11-19 19:38 ` Alan Third
2022-04-18 11:32 ` bug#22818: 25.0.91; nextstep/Emacs.app Crash ns_compute_glyph_string_overhangs Lars Ingebrigtsen
2022-04-18 11:44 ` Aaron S. Hawley
2022-04-18 11:45 ` 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=20161119111823.GA66770@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=22818@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=josh@berdine.net \
/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).