From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 46494@debbugs.gnu.org
Subject: bug#46494: 28.0.50; [native-comp] Problems with async background compile
Date: Sat, 13 Feb 2021 22:24:08 +0200 [thread overview]
Message-ID: <83zh07btsn.fsf@gnu.org> (raw)
In-Reply-To: <86czx3iush.fsf@gmail.com> (message from Andy Moreton on Sat, 13 Feb 2021 20:20:46 +0000)
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Sat, 13 Feb 2021 20:20:46 +0000
>
> >> c) Quitting emacs when async compilation processes are running sometimes
> >> causes crashes in the compile processes, which show the emacs abort
> >> dialog (once for each async process). The dialogs disappear after a
> >> short delay (presumably due to the parent emacs having exited).
> >
> > Do the crashing processes run Emacs or do they run the compiler? If
> > the former, can you attach GDB to them and show backtraces?
>
> I think it is the compiler processes: I get multiple emacs abort dialogs
> rather than just one. I've tried attaching gdb, which does not manage to
> produce a backtrace.
I think it's Emacs that crashes, because otherwise why is the Emacs
abort di1alog shown?
next prev parent reply other threads:[~2021-02-13 20:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 16:58 bug#46494: 28.0.50; [native-comp] Problems with async background compile Andy Moreton
2021-02-13 18:12 ` Eli Zaretskii
2021-02-13 20:20 ` Andy Moreton
2021-02-13 20:24 ` Eli Zaretskii [this message]
2021-02-14 8:01 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-14 15:31 ` Eli Zaretskii
2021-02-14 18:28 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-14 19:11 ` Eli Zaretskii
2021-02-20 10:37 ` Eli Zaretskii
2021-02-20 12:09 ` Andy Moreton
2021-02-20 12:54 ` Eli Zaretskii
2021-02-20 16:40 ` Andy Moreton
2021-02-20 16:54 ` Eli Zaretskii
2021-02-20 17:30 ` Andy Moreton
2021-02-20 17:37 ` Eli Zaretskii
2021-03-07 14:34 ` Eli Zaretskii
2021-03-08 0:19 ` Andy Moreton
2021-03-08 3:27 ` Eli Zaretskii
2021-02-21 21:22 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-22 3:28 ` Eli Zaretskii
2021-02-22 19:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 16:53 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 18:34 ` Eli Zaretskii
2021-03-16 20:10 ` Andy Moreton
2021-03-16 20:48 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83zh07btsn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46494@debbugs.gnu.org \
--cc=andrewjmoreton@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).