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 22:33:23 +0300 [thread overview]
Message-ID: <835y95fe64.fsf@gnu.org> (raw)
In-Reply-To: <7viubPQBitOqW2lvRK1P_aP6NjiS05pc86HGIH8yUyCZGabZgL5Hb3YAdm9efSCsxPb7yxW55zGhfZfE2PUjkZesUSharobfMDC3-JTEL1E=@protonmail.com> (message from Seppo Ronkainen on Sat, 06 May 2023 19:12:53 +0000)
> Date: Sat, 06 May 2023 19:12:53 +0000
> From: Seppo Ronkainen <sodr80@protonmail.com>
> Cc: 63283@debbugs.gnu.org
>
> sure, here are captures of gdb and system-configuration-features from two build variants of 29.0.90 and one 26.3
Thanks. Please repeat this session again, and this time, when Emacs
aborts and GDB shows its prompt, do this:
(gdb) thread 1
(gdb) pp fontset
If GDB says that it doesn't know the command "pp", type
(gdb) source /path/to/emacs/src/.gdbinit
(gdb) pp fontset
and post everything GDB prints after that.
And one more data point: in the same session do this:
(gdb) frame 2
(gdb) print font_driver_list
(gdb) print f->font_driver_list
and show the values GDB prints.
next prev parent reply other threads:[~2023-05-06 19:33 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
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 [this message]
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=835y95fe64.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).