GNU bug report logs - #66416
29.1; Crashes when visiting HELLO file with pgtk on Wayland

Previous Next

Full log

Message #125 received at 66416 <at> debbugs.gnu.org (full text, mbox):

From: Björn Bidar <bjorn.bidar <at> thaodan.de>
To: Po Lu <luangruo <at> yahoo.com>
Cc: Mattias Engdegård <mattiase <at> acm.org>,
 Eli Zaretskii <eliz <at> gnu.org>, 66416 <at> debbugs.gnu.org, yguo <at> posteo.net
Subject: Re: bug#66416: 29.1; pgtk build crashes due to ftcrfont
Date: Tue, 16 Apr 2024 17:19:24 +0300

Po Lu <luangruo <at> yahoo.com> writes:

> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>> As for the cause of this -- some problem in ftcrfont_draw -- maybe Po
>> Lu can suggest some ideas.  I guess we should try to understand what
>> kind of X error was caused here?
>
> Yes.  Please switch to the frame of the call to x_error_quitter, there
> run:
>
>   (gdb) p *event
>   (gdb) shell xdpyinfo -ext all
>
> and respond the output of these commands.

I didn't trigger the error on purpose but by accident. A package used
obarray wrong (with nil instead of 0) which caused an error like this:
(wrong-type-argument obarrayp [nil nil nil nil nil nil nil nil nil nil
nil nil nil])

The error did not immediately cause a crash but some time after.

I have a gdb attached, If get a crash now I can send these outputs.

I'm not sure if this related but sometimes Emacs is stuck rendering
org-mode buffers till it receives SIGUSR2 or user input.
Requests such as emacsclient -nc don't reach Emacs until either of the
two above happens.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.