From: Eli Zaretskii <eliz@gnu.org>
To: Josh Berdine <josh@berdine.net>
Cc: 22818@debbugs.gnu.org
Subject: bug#22818: 25.1.1 Emacs.app crash ns_compute_glyph_string_overhangs
Date: Sat, 19 Nov 2016 09:07:50 +0200 [thread overview]
Message-ID: <83twb4aqwp.fsf@gnu.org> (raw)
In-Reply-To: <jk60igfumowk3e.fsf@fb.com> (message from Josh Berdine on Fri, 18 Nov 2016 21:31:49 +0000)
> From: Josh Berdine <josh@berdine.net>
> Date: Fri, 18 Nov 2016 21:31:49 +0000
>
> (lldb) c
> Process 42346 resuming
> Process 42346 stopped
> * thread #1: tid = 0x449aca, 0x00000001001b5767 Emacs-x86_64-10_9`ns_compute_glyph_string_overhangs + 119, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0xd0)
> frame #0: 0x00000001001b5767 Emacs-x86_64-10_9`ns_compute_glyph_string_overhangs + 119
> Emacs-x86_64-10_9`ns_compute_glyph_string_overhangs:
> -> 0x1001b5767 <+119>: movq 0xd0(%rdi), %rax
> 0x1001b576e <+126>: cmpq $0x7e00, (%rax) ; imm = 0x7E00
> 0x1001b5775 <+133>: jne 0x1001b579b ; <+171>
> 0x1001b5777 <+135>: xorl %eax, %eax
> (lldb) bt
> * thread #1: tid = 0x449aca, 0x00000001001b5767 Emacs-x86_64-10_9`ns_compute_glyph_string_overhangs + 119, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0xd0)
> * frame #0: 0x00000001001b5767 Emacs-x86_64-10_9`ns_compute_glyph_string_overhangs + 119
> frame #1: 0x00000001000379d7 Emacs-x86_64-10_9`draw_glyphs + 3415
> frame #2: 0x0000000100036c16 Emacs-x86_64-10_9`x_write_glyphs + 166
> frame #3: 0x0000000100009e3e Emacs-x86_64-10_9`update_window_line + 670
> frame #4: 0x0000000100005edc Emacs-x86_64-10_9`update_window + 4588
> frame #5: 0x00000001000046a4 Emacs-x86_64-10_9`update_window_tree + 116
> frame #6: 0x00000001000044e7 Emacs-x86_64-10_9`update_frame + 135
Can you convert the address in frame #0 into line numbers? Judging by
the faulting address, 0xd0, some pointer in
ns_compute_glyph_string_overhangs is a null pointer, but it's hard to
tell which one without the line number information.
next prev parent reply other threads:[~2016-11-19 7:07 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 [this message]
2016-11-19 10:07 ` Alan Third
2016-11-19 10:27 ` Eli Zaretskii
2016-11-19 11:18 ` Alan Third
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=83twb4aqwp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22818@debbugs.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).