unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Fri, 11 Aug 2023 18:24:35 +0300	[thread overview]
Message-ID: <831qg9haa4.fsf@gnu.org> (raw)
In-Reply-To: <CA+cG9GyB+dPeoeHuwvsJ1Mf3WDeMg_VFpM8E3cW8+cPKV4d1KA@mail.gmail.com> (message from 张云峰 on Fri, 11 Aug 2023 22:21:11 +0800)

> From: 张云峰 <zhangyunfeng0101@gmail.com>
> Date: Fri, 11 Aug 2023 22:21:11 +0800
> Cc: 65198@debbugs.gnu.org
> 
> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
> 0x0000555555616206 in produce_glyphless_glyph (it=0x7fffffff6cc0,
> for_no_font=for_no_font@entry=false, acronym=acronym@entry=0x0) at
> xdisp.c:31791
> 31791 font = face->font ? face->font : FRAME_FONT (it->f);
> (gdb) p it->face_id
> $1 = 0
> (gdb) p it->c
> $2 = 9888
> (gdb) p FRAME_FONT(it->f)
> No symbol "FRAME_FONT" in current context.
> (gdb) p (it->f)->output_data.x->font

Since it turns out this is a PGTK build, please show this instead:

  (gdb) p (it->f)->output_data.pgtk->font





      parent reply	other threads:[~2023-08-11 15:24 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
     [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 [this message]

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=831qg9haa4.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 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).