From: Eli Zaretskii <eliz@gnu.org>
To: 张云峰 <zhangyunfeng0101@gmail.com>
Cc: 65198@debbugs.gnu.org
Subject: bug#65198: 29.1; Emacs29.1 crash in function face_for_font
Date: Thu, 10 Aug 2023 13:06:35 +0300 [thread overview]
Message-ID: <83r0obi53o.fsf@gnu.org> (raw)
In-Reply-To: <CA+cG9Gz46X=rwMPSwJR-R6D6rdZf+9wdmFez2aRtzoE7EtkGvQ@mail.gmail.com> (message from 张云峰 on Thu, 10 Aug 2023 17:57:20 +0800)
> From: 张云峰 <zhangyunfeng0101@gmail.com>
> Date: Thu, 10 Aug 2023 17:57:20 +0800
>
> ;;;;; GDB INFO ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>
> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
> 0x00005555556859b8 in face_for_font (f=0x555561746d40, font_object=0x555558465ec5,
> base_face=base_face@entry=0x0) at xfaces.c:4931
> 4931 base_face = base_face->ascii_face;
> (gdb) bt
> #0 0x00005555556859b8 in face_for_font (f=0x555561746d40, font_object=0x555558465ec5,
> base_face=base_face@entry=0x0) at xfaces.c:4931
> #1 0x00005555555ee682 in get_next_display_element (it=it@entry=0x7fffffff6c90) at xdisp.c:8322
> #2 0x00005555555eacb0 in move_it_in_display_line_to (it=it@entry=0x7fffffff6c90,
> to_charpos=to_charpos@entry=412, to_x=to_x@entry=2147483647, op=op@entry=(MOVE_TO_X
> | MOVE_TO_POS))
> at xdisp.c:9829
> #3 0x00005555555f002a in move_it_to (it=0x7fffffff6c90, to_charpos=412, to_x=<optimized out>,
> to_y=<optimized out>, to_vpos=<optimized out>, op=11) at xdisp.c:10500
> #4 0x0000555555604e4e in window_text_pixel_size
> (window=<optimized out>, from=<optimized out>, to=<optimized out>, x_limit=0x1ce2,
> y_limit=<optimized out>, mode_lines=0x0, ignore_line_at_end=0x0) at xdisp.c:11455
> #5 0x0000555555605ae6 in Fwindow_text_pixel_size (window=0x555561746f95, from=0x0,
> to=0x0, x_limit=0x1ce2, y_limit=0xaf2, mode_lines=0x0, ignore_line_at_end=0x0) at xdisp.c:11629
> #6 0x0000555555771442 in funcall_subr (subr=0x555555d0e5a0 <Swindow_text_pixel_size>,
> numargs=numargs@entry=5, args=args@entry=0x7ffff0bff1f0) at eval.c:3046
Thanks. Any chance of a recipe to reproduce this crash?
The backtrace indicates that the code which crashed was called from a
timer function -- any idea what timer was that?
next prev parent reply other threads:[~2023-08-10 10:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 9:57 bug#65198: 29.1; Emacs29.1 crash in function face_for_font 张云峰
2023-08-10 10:06 ` Eli Zaretskii [this message]
[not found] ` <CA+cG9GxATqwi7-aFEvma0zi3AZM5y6eshU510oPFohuKwhHF4w@mail.gmail.com>
2023-08-10 17:22 ` Eli Zaretskii
2023-08-10 17:58 ` 张云峰
2023-08-10 18:36 ` Eli Zaretskii
2023-08-11 0:15 ` 张云峰
2023-08-11 0:50 ` 张云峰
2023-08-11 6:12 ` Eli Zaretskii
2023-08-11 14:21 ` 张云峰
2023-08-11 14:55 ` 张云峰
2023-08-11 15:30 ` Eli Zaretskii
2023-08-11 16:14 ` 张云峰
2023-08-12 6:39 ` Eli Zaretskii
2023-08-11 15:24 ` Eli Zaretskii
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=83r0obi53o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65198@debbugs.gnu.org \
--cc=zhangyunfeng0101@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 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.