From: Eli Zaretskii <eliz@gnu.org>
To: Seppo Ronkainen <sodr80@protonmail.com>
Cc: 63283@debbugs.gnu.org
Subject: bug#63283: Emacs crash within fontset
Date: Sat, 06 May 2023 13:20:09 +0300 [thread overview]
Message-ID: <835y95hicm.fsf@gnu.org> (raw)
In-Reply-To: <O0y0FC8UdwKgg50s40rJP5ahH61bZfOHqEE6soqVPHCOnUr0PvUNonc9GL2dmbHDWiwZBu_6Pc29DlpXNQE80C5vQJRrgGza-nVbU_OczfY=@protonmail.com> (message from Seppo Ronkainen on Fri, 05 May 2023 21:19:18 +0000)
[Please use Reply All to reply, so that the bug address is on the CC
list, and this discussion is recorded by our bug tracker.]
> Date: Fri, 05 May 2023 21:19:18 +0000
> From: Seppo Ronkainen <sodr80@protonmail.com>
>
> I was not aware about report-emacs-bug thanks for the guidance
>
> Following instructions from (share/emacs/29.0.90/etc/DEBUG:19) I rebuilt with options
>
> ./configure --enable-checking='yes,glyphs' --enable-check-lisp-object-type \
> CFLAGS='-O0 -g3'
>
>
>
> TL;DR
> Now it looks as if (of course) Emacs never crashed, but it seems as if insufficient font data caused an abort is that right? Hope this helps
>
> fontset.c:970: Emacs fatal error: assertion failed: fontset_id_valid_p (face->fontset)
> Fatal error 6: Aborted
Thanks, but this is not enough info to find the root cause of the
problem. Please run Emacs under GDB, like this:
$ gdb /path/to/src/emacs
...
(gdb) run
Then, when Emacs crashes or aborts, GDB will kick in and show its
"(gdb)" prompt. Please type at the GDB prompt:
(gdb) thread apply all bt
and post here everything that GDB prints in response.
Also, please show what this displays inside Emacs built --without-all:
M-: system-configuration-features RET
next prev parent reply other threads:[~2023-05-06 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 19:04 bug#63283: Emacs crash within fontset Seppo Ronkainen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-05 3:19 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-05 4:37 ` Eli Zaretskii
[not found] ` <O0y0FC8UdwKgg50s40rJP5ahH61bZfOHqEE6soqVPHCOnUr0PvUNonc9GL2dmbHDWiwZBu_6Pc29DlpXNQE80C5vQJRrgGza-nVbU_OczfY=@protonmail.com>
2023-05-06 10:20 ` Eli Zaretskii [this message]
2023-05-06 19:12 ` Seppo Ronkainen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-06 19:33 ` Eli Zaretskii
2023-05-06 22:36 ` Seppo Ronkainen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-07 6:48 ` Eli Zaretskii
2023-05-08 21:22 ` Seppo Ronkainen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-09 5:26 ` 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
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=835y95hicm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63283@debbugs.gnu.org \
--cc=sodr80@protonmail.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).