unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Anand Tamariya <atamariya@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: bug#54188: Crash when eval-ing font test elisp code
Date: Thu, 29 Aug 2024 10:24:56 +0530	[thread overview]
Message-ID: <CADm7Y4kyd+b0ugzBHJumOaYsvSAabzb-r2SUtO7XuUvNcdP_vQ@mail.gmail.com> (raw)
In-Reply-To: <86ikvkh66z.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 775 bytes --]

On Wed, Aug 28, 2024 at 11:37 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Anand Tamariya <atamariya@gmail.com>
> > Date: Wed, 28 Aug 2024 20:34:17 +0530
> > Cc: emacs-devel@gnu.org
> >
> >  Can you give examples of such fonts, and show a GDB C-level backtrace
> >  from the crash?
> >
> > I always get the crash when I scroll to the next page after the page in
> the screenshot. I can't point out the
> > specific font. So I have listed the possible fonts on the next screen.
>
> Thanks.  What version of Emacs is this?
>
This problem is not present in the latest version (tested with Emacs 29.4).
To summarize, if you're facing the crash, do one of the following:
- Remove the characters 180, 166 and 216.
- Upgrade to the latest version of Emacs

[-- Attachment #2: Type: text/html, Size: 1282 bytes --]

  reply	other threads:[~2024-08-29  4:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28  8:47 bug#54188: Crash when eval-ing font test elisp code 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 [this message]
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

  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=CADm7Y4kyd+b0ugzBHJumOaYsvSAabzb-r2SUtO7XuUvNcdP_vQ@mail.gmail.com \
    --to=atamariya@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).