From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Po Lu" <luangruo@yahoo.com>,
"Björn Bidar" <bjorn.bidar@thaodan.de>,
yguo@posteo.net, 66416@debbugs.gnu.org
Subject: bug#66416: 29.1; pgtk build crashes due to ftcrfont
Date: Tue, 16 Apr 2024 15:13:49 +0200 [thread overview]
Message-ID: <23AB6396-AC35-403A-A22B-F1DC02855D36@gmail.com> (raw)
In-Reply-To: <86h6g1jyf2.fsf@gnu.org>
16 apr. 2024 kl. 14.16 skrev Eli Zaretskii <eliz@gnu.org>:
>> #71 0x000055fb2cc1435b in wrong_type_argument (predicate=<optimized out>, value=<optimized out>) at ../../emacs-30.0.50.5934.0fab2649e28/src/data.c:142
>> #72 0x000055fb2cc16e84 in check_obarray_slow (obarray=<optimized out>) at /usr/src/debug/emacs-30.0.50.5990.9b755244bf0/src/lread.c:4914
>> #73 0x000055fb2ce36467 in check_obarray (obarray=XIL(0x55fc40b4ea8d)) at ../../emacs-30.0.50.5934.0fab2649e28/src/lisp.h:2465
>> #74 Fintern (string=XIL(0x55fb52250fe4), obarray=<optimized out>) at /usr/src/debug/emacs-30.0.50.5990.9b755244bf0/src/lread.c:5034
>> #75 0x000055fb2cdfb15d in funcall_subr (subr=0x55fb2d45dea0 <Sintern>, numargs=numargs@entry=2, args=args@entry=0x7ffdeb3b1448) at ../../emacs-30.0.50.5987.9a79db506e3/src/eval.c:3092
It looks like `intern` was called with a second argument that wasn't of a valid type (obarray or nonempty vector starting with 0) but that's as far as it goes, and doesn't indicate anything wrong in the obarray code.
We would need to catch it in the act with a debugger attached, and/or know what Lisp code is being executed.
next prev parent reply other threads:[~2024-04-16 13:13 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 20:32 bug#66416: 29.1; Crashes when visiting HELLO file with pgtk on Wayland Yuchen Guo
2023-10-09 10:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-09 11:19 ` Eli Zaretskii
2023-10-09 11:24 ` Eli Zaretskii
[not found] ` <87bkd7k6b8.fsf@lan>
2023-10-09 18:45 ` Eli Zaretskii
2023-10-09 19:07 ` Yuchen Guo
2023-10-10 2:30 ` Eli Zaretskii
2023-10-10 5:26 ` Yuchen Guo
2023-10-10 12:08 ` Eli Zaretskii
2023-10-10 12:59 ` Yuchen Guo
2023-10-10 13:40 ` Eli Zaretskii
2023-10-10 16:26 ` Yuchen Guo
2023-10-11 11:31 ` Eli Zaretskii
2023-10-11 12:45 ` Yuchen Guo
2023-10-11 13:12 ` Eli Zaretskii
2023-10-10 4:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-09 18:44 ` bug#66416: Coredump Yuchen Guo
2023-10-12 7:46 ` bug#66416: GDB output from new crash Yuchen Guo
2023-10-12 8:12 ` Yuchen Guo
2023-10-12 10:23 ` Eli Zaretskii
2023-10-12 11:22 ` Yuchen Guo
2023-10-12 12:31 ` Eli Zaretskii
2023-10-12 13:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-12 14:28 ` Yuchen Guo
2023-10-12 14:42 ` Yuchen Guo
2023-10-14 11:00 ` Eli Zaretskii
2023-10-14 11:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 12:38 ` Eli Zaretskii
2023-10-14 12:40 ` Yuchen Guo
2023-10-14 12:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 14:23 ` Yuchen Guo
2023-10-14 15:40 ` Eli Zaretskii
2023-10-15 1:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-15 5:54 ` Yuchen Guo
2023-10-12 11:43 ` Yuchen Guo
2023-10-14 19:14 ` bug#66416: 29.1; pgtk build crashes due to ftcrfont Yuchen Guo
2024-04-16 0:27 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87mspui23l.fsf@>
2024-04-16 12:16 ` Eli Zaretskii
2024-04-16 13:13 ` Mattias Engdegård [this message]
2024-04-16 14:21 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 13:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 14:19 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=23AB6396-AC35-403A-A22B-F1DC02855D36@gmail.com \
--to=mattias.engdegard@gmail.com \
--cc=66416@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=yguo@posteo.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).