From: Pieter van Oostrum <pieter-l@vanoostrum.org>
To: Alan Third <alan@idiocy.org>
Cc: 44850@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
pieter@vanoostrum.org
Subject: bug#44850: 27.1; Emacs crash in font handling with font-backend ns
Date: Sat, 28 Nov 2020 15:23:54 +0100 [thread overview]
Message-ID: <lxmtz1impx.fsf@cochabamba.vanoostrum.org> (raw)
In-Reply-To: <20201127101918.GC26836@breton.holly.idiocy.org> (Alan Third's message of "Fri, 27 Nov 2020 10:19:18 +0000")
Alan Third <alan@idiocy.org> writes:
> On Fri, Nov 27, 2020 at 11:04:35AM +0100, Lars Ingebrigtsen wrote:
>> Alan Third <alan@idiocy.org> writes:
>>
>> > It's bug#44349. It doesn't look like that bug report went anywhere.
>>
>> Right; I've now merged these two bug reports.
>
> I'm not convinced that bug report is related to the original report in
> this bug report. One is in emacs string handling code, the other is in
> macfont.m code.
I think my original bug report is a different issue. Actually I am running a nightly build of Emacs 28 now (https://emacsformacosx.com/emacs-builds/Emacs-2020-10-25_01-40-16-10ea719abcde4f2ee40e717eb846fe93f51d5d79-universal.dmg), and it gives me the same segfault as Emacs 27.
However, when I compile revision 10ea719abcde4f2ee40e717eb846fe93f51d5d79 it gives the doprnt crash. Very strange.
So I would prefer not to merge these bug reports.
--
Pieter van Oostrum
www: http://pieter.vanoostrum.org/
PGP key: [8DAE142BE17999C4]
next prev parent reply other threads:[~2020-11-28 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 18:09 bug#44850: 27.1; Emacs crash in font handling with font-backend ns Pieter van Oostrum
2020-11-25 14:48 ` Pieter van Oostrum
2020-11-26 11:01 ` Lars Ingebrigtsen
2020-11-26 17:26 ` Pieter van Oostrum
2020-11-26 19:23 ` Eli Zaretskii
2020-11-27 8:16 ` Lars Ingebrigtsen
2020-11-27 9:55 ` Alan Third
2020-11-27 10:04 ` Lars Ingebrigtsen
2020-11-27 10:19 ` Alan Third
2020-11-28 14:23 ` Pieter van Oostrum [this message]
2020-11-27 12:23 ` Eli Zaretskii
2020-11-29 18:22 ` Alan Third
2020-11-27 17:16 ` Mattias Engdegård
2020-11-27 18:44 ` Eli Zaretskii
2020-11-29 9:45 ` Lars Ingebrigtsen
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=lxmtz1impx.fsf@cochabamba.vanoostrum.org \
--to=pieter-l@vanoostrum.org \
--cc=44850@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=larsi@gnus.org \
--cc=pieter@vanoostrum.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).