From: Alan Third <alan@idiocy.org>
To: Andrii Kolomoiets <andreyk.mad@gmail.com>
Cc: 44058-done@debbugs.gnu.org, Vincent Zhang <seagle0128@gmail.com>,
Dale Sedivec <dale@codefu.org>
Subject: bug#44058: Crashing maybe due to NS internal borders (c4c5db3de70b55f8bc03c9fee35e29d60f41f16e)
Date: Thu, 22 Oct 2020 20:09:21 +0100 [thread overview]
Message-ID: <028b9317-78c7-450b-b639-55cee4c160e7_IMAP_ADDED_MISSING@EDGAR> (raw)
In-Reply-To: <m2r1pq68rh.fsf@gmail.com>
On Thu, Oct 22, 2020 at 10:05:06AM +0300, Andrii Kolomoiets wrote:
> Dale Sedivec <dale@codefu.org> writes:
>
> > Hi, I'm seeing something similar, and indeed I'm seeing it on master
> > (and also native-comp, but this message is about master). We have
> > clear_garbaged_frames in common on our stack, at least.
>
> You may be interested in the small patch by Alan from Bug#43973:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43973#11
>
> Emacs was crashing for me also with the clear_garbaged_frames on the
> stack. Since the patch was applied, Emacs does not crash.
Hmm, I got so caught up in the other bug that I forgot about that one.
I'll push the fix to master now.
Dale and Vincent, if this doesn't fix your crash please let us know to
reopen this bug report.
--
Alan Third
next prev parent reply other threads:[~2020-10-22 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 6:33 bug#44058: 28.0.50; native-comp builds crashs Vincent Zhang
2020-10-19 7:25 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-22 6:31 ` bug#44058: Crashing maybe due to NS internal borders (c4c5db3de70b55f8bc03c9fee35e29d60f41f16e) Dale Sedivec
2020-10-22 7:05 ` Andrii Kolomoiets
2020-10-22 19:09 ` Alan Third [this message]
2020-10-23 20:58 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-24 21:37 ` Dale Sedivec
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=028b9317-78c7-450b-b639-55cee4c160e7_IMAP_ADDED_MISSING@EDGAR \
--to=alan@idiocy.org \
--cc=44058-done@debbugs.gnu.org \
--cc=andreyk.mad@gmail.com \
--cc=dale@codefu.org \
--cc=seagle0128@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 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.