Subject: Re: bug#66416: 29.1; pgtk build crashes due to ftcrfont

From: Mattias Engdegård <[email-masked]>
Date: Tue, 16 Apr 2024 15:13:49 +0200

16 apr. 2024 kl. 14.16 skrev Eli Zaretskii <[email-masked]>:

>> #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.