unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Vojta via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 68940@debbugs.gnu.org
Subject: bug#68940: 29.2; Random crashes in face for char / font
Date: Tue, 06 Feb 2024 22:59:23 +0100	[thread overview]
Message-ID: <m2a5od6y69.fsf@me.com> (raw)
In-Reply-To: <86sf25zgjx.fsf@gnu.org>

> Yes, what's important is to see what is value of base_face at entry to
> face_for_font -- it sounds like that's an invalid face doer some
> reason.  Do you have any customizations of the fontsets?

No, no fontsets customizations.

This whole thing is getting weirder. I've recompiled Emacs w/ "-O0 -g3"
and two new things appeared:

1) Invalid read syntax: #

Warning (initialization): An error occurred while loading
‘/Users/zrzka/.emacs.d/init.el’

This is random as well, and it happens frequently (30% of Emacs
launches).

2) A new crash happened

It is hard to reproduce it in my "while true; lldb ...; done" loop with
this error (a lot of manual interventios required), but managed to
capture another backtrace:

https://gist.github.com/zrzka/7855634a46adeacb2fa7e8f861e39106

All this, purely random, undefined behavior?

Recompiled again, this time I've added "-fsanitize=address" (full flags
"-O0 -g3 -fsanitize=address"), and the first thing (Invalid read syntax
#) is gone. Leaving it running for the whole night, to see what's gonna
happen now.

If it won't reveal anything, I will switch back to "-O0 -g3", and will
start bisecting 29.1 -> 29.2 changes.





  reply	other threads:[~2024-02-06 21:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 22:46 bug#68940: 29.2; Random crashes in face for char / font Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 12:23 ` Eli Zaretskii
2024-02-06 12:29   ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 14:14     ` Eli Zaretskii
2024-02-06 15:55       ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 16:46         ` Eli Zaretskii
2024-02-06 21:59           ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-02-07  7:41             ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-07 13:01               ` Eli Zaretskii
2024-02-08  5:42               ` Gerd Möllmann
2024-02-08  7:14                 ` Eli Zaretskii
2024-02-08  7:31                   ` Gerd Möllmann
2024-02-07 12:32             ` Eli Zaretskii
2024-02-07 12:50               ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08  6:07                 ` Gerd Möllmann
2024-02-08  9:00                   ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08  9:56                     ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08 10:35                       ` Gerd Möllmann
2024-02-09  7:22                         ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08 10:17                     ` Gerd Möllmann

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=m2a5od6y69.fsf@me.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=68940@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rvojta@me.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).