all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vordoo 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: 54188@debbugs.gnu.org
Subject: bug#54188: Crash when eval-ing font test elisp code
Date: Mon, 28 Feb 2022 09:09:04 +0200	[thread overview]
Message-ID: <d73500e6-4c0b-71c5-8a34-37f5185d426c@yahoo.com> (raw)
In-Reply-To: <8335k3oeh0.fsf@gnu.org>

On 2/28/22 05:30, Eli Zaretskii wrote:
>> 3. Emacs crash
>>
>> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
>> 0x0000555555790ec1 in fontset_find_font ()
> I cannot reproduce this here.
>
> In general, trying to use Emacs with arbitrary fonts is not a good
> idea, as not every font can be used by Emacs.

Thanks for your prompt response!


1. I can ditch this code. It's from: 
https://www.emacswiki.org/emacs/GoodFonts. I'll try updating them.


2. On the other hand, throwing at emacs anything "reasonable" without it 
crashing is an advantage. What is reasonable is not my call :-o


3. The code did work nice a couple of times. The crash started after 
removing/adding fonts to the system. I can try retracing the culprit 
font, if you find it worthwhile, or just move on.



Have a great day!







  reply	other threads:[~2022-02-28  7:09 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50f9bd97-02a4-4b0d-0eae-54e804293219.ref@yahoo.com>
2022-02-27 20:33 ` bug#54188: Crash when eval-ing font test elisp code Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28  3:30   ` Eli Zaretskii
2022-02-28  7:09     ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-28 12:19       ` Eli Zaretskii
2022-02-28 21:44         ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 12:55           ` Eli Zaretskii
2022-03-01 15:23             ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 17:38               ` Eli Zaretskii
2022-03-01 18:50                 ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 19:37                   ` Eli Zaretskii
2022-03-01 20:08                     ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 20:33                       ` Eli Zaretskii
2022-03-01 21:51                         ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03  9:46                           ` Eli Zaretskii
2022-03-03 12:46                             ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 14:05                               ` Eli Zaretskii
2022-03-03 14:16                                 ` Lars Ingebrigtsen
2022-03-03 14:25                                   ` Eli Zaretskii
2022-03-03 14:51                                     ` Lars Ingebrigtsen
2022-03-03 15:04                                       ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 15:22                                         ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 14:39                                   ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 14:49                                     ` jeff
2022-02-28  9:41   ` Lars Ingebrigtsen
2024-08-28  8:47 Anand Tamariya
2024-08-28 12:37 ` Eli Zaretskii
2024-08-28 15:04   ` Anand Tamariya
2024-08-28 15:29     ` Pip Cet
2024-08-28 15:54       ` Eli Zaretskii
2024-08-28 18:07     ` Eli Zaretskii
2024-08-29  4:54       ` Anand Tamariya
2024-08-29  5:11         ` Yuri Khan
2024-08-29  6:02         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d73500e6-4c0b-71c5-8a34-37f5185d426c@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54188@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=vordoo@yahoo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.