unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kirill A. Korinsky" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: 50641@debbugs.gnu.org
Subject: bug#50641: 28.0.50; Crash on macOS
Date: Sat, 23 Oct 2021 22:21:18 +0200	[thread overview]
Message-ID: <DBF2B5DB-587A-4BA0-BEC9-05DC798D4D8C@korins.ky> (raw)
In-Reply-To: <YXRncfO3sSQ7u9CP@idiocy.org>


[-- Attachment #1.1: Type: text/plain, Size: 914 bytes --]

It crashes quite rare, and I have no idea how to easy reproduce it.

Anyway, I'm a bit limited with bisect because of bug #50946 which was introduced in 71857d4106 (this summer) and fixed d3a832a61a (beggining of October).

--
wbr, Kirill

> On 23. Oct 2021, at 21:50, Alan Third <alan@idiocy.org> wrote:
> 
> On Wed, Oct 20, 2021 at 10:34:23PM +0200, Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors wrote:
>> Crash occurs disappear on last master.
>> 
>> But it crashed on master "month ago".
>> 
>> I'll updated this bug if emacs crashes again.
> 
> So we've, possibly inadvertently, fixed it on master, but not
> emacs-28...
> 
> Since I can't replicate this I'm afraid all I can suggest is that you
> do a git bisect and try to find the commit that fixes it on the master
> branch.
> 
> It could be extremely time consuming.
> --
> Alan Third


[-- Attachment #1.2: Type: text/html, Size: 2126 bytes --]

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-10-23 20:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 14:10 bug#50641: 28.0.50; Crash on macOS Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-19 15:16 ` Stefan Kangas
2021-09-19 22:48   ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-29 10:51     ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-29 18:59 ` Alan Third
2021-09-29 19:02   ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-20 13:25     ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-20 15:59       ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-20 20:20         ` Alan Third
2021-10-20 20:34           ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-23 19:50             ` Alan Third
2021-10-23 20:21               ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-11-02 20:17                 ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-22 13:20                   ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-22 18:27                     ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 11:44                       ` Lars Ingebrigtsen
2022-08-26 12:32                         ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 12:52                           ` 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=DBF2B5DB-587A-4BA0-BEC9-05DC798D4D8C@korins.ky \
    --to=bug-gnu-emacs@gnu.org \
    --cc=50641@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=kirill@korins.ky \
    /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).