From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59861-done@debbugs.gnu.org,
Markus von der Heyde <markus.von.der.heyde@gmail.com>
Subject: bug#59861: 27.1; seg fault using utf8 char in text
Date: Sun, 3 Sep 2023 02:38:24 -0700 [thread overview]
Message-ID: <CADwFkmmbG-toezt0Oty321EeY9Ji7Xg-oM8Ft+=hCs9YyCVg7g@mail.gmail.com> (raw)
In-Reply-To: <83tu285ou6.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 06 Dec 2022 21:12:01 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> [Please use Reply All to reply, so that the bug tracker is CC'ed.]
>
>> Date: Tue, 6 Dec 2022 20:00:17 +0100
>> From: Markus von der Heyde <markus.von.der.heyde@gmail.com>
>>
>> No crash here, neither in Emacs 27.1 nor in the what will soon be Emacs 29.
>>
>> Hi Eli,
>>
>> have you tried to load the attached <crash.txt> file or just typed an "*" aka ASCII42?
>
> I visited the file you attached.
>
>> The star (∗) was some utf8 char (!= *). I have no quick way to name the actual utf-8 code... sorry.
>
> It's U+2217.
>
> Did you try using a different font, or forcing a non-default font backend?
>
> And which version of HarfBuzz do you have installed?
More information was requested, but none was given within 9 months, so
I'm closing this bug. If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.
prev parent reply other threads:[~2023-09-03 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 15:34 bug#59861: 27.1; seg fault using utf8 char in text Markus von der Heyde
2022-12-06 17:15 ` Eli Zaretskii
[not found] ` <17805d1f-4a66-6c1d-1cb0-1d46d3a25f6d@gmail.com>
2022-12-06 19:12 ` Eli Zaretskii
2023-09-03 9:38 ` Stefan Kangas [this message]
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='CADwFkmmbG-toezt0Oty321EeY9Ji7Xg-oM8Ft+=hCs9YyCVg7g@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=59861-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=markus.von.der.heyde@gmail.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).