From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 13653-done@debbugs.gnu.org
Subject: bug#13653: 24.2.93; cygw32 in daemon mode aborts in response to kill command
Date: Sun, 6 Dec 2020 17:50:24 -0500 [thread overview]
Message-ID: <50bbbcc6-9d9e-3807-4e7c-4dcc3df0938e@cornell.edu> (raw)
In-Reply-To: <83h7oyaga4.fsf@gnu.org>
On 12/6/2020 2:25 PM, Eli Zaretskii wrote:
>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Date: Sun, 06 Dec 2020 20:14:27 +0100
>> Cc: 13653@debbugs.gnu.org
>>
>> Ken Brown <kbrown@cornell.edu> writes:
>>
>>> In the cygw32 build, start emacs in daemon mode:
>>>
>>> $ emacs --daemon -Q
>>>
>>> Now kill it from the terminal:
>>>
>>> $ kill PID
>>>
>>> The result is an Emacs Abort Dialog box saying a fatal error has
>>> occurred and asking me if I want to attach a debugger. I have two
>>> problems with this. First, a kill command shouldn't cause emacs to
>>> abort. Second, I don't think the cygw32 build should ever pop up an
>>> abort dialog box. None of the other emacs builds on Cygwin do this,
>>> so it's surprising and confusing to users.
>>
>> (This bug report unfortunately got no response at the time.)
>>
>> Are you still seeing this problem in more recent Emacs versions?
>
> Assuming that Ken says this is still an issue: how does 'kill' work in
> its Cygwin version? Specifically, is it possible that it runs the
> signal handler in a separate thread, like what Windows does with
> SIGINT handlers of console programs if one types Ctrl-C? If so, I
> think I know the reason and can describe the details; fixing that is
> not trivial, to say the least.
No, it's not an issue anymore. Closing.
Ken
prev parent reply other threads:[~2020-12-06 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 16:39 bug#13653: 24.2.93; cygw32 in daemon mode aborts in response to kill command Ken Brown
2020-12-06 19:14 ` Lars Ingebrigtsen
2020-12-06 19:25 ` Eli Zaretskii
2020-12-06 22:50 ` Ken Brown [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=50bbbcc6-9d9e-3807-4e7c-4dcc3df0938e@cornell.edu \
--to=kbrown@cornell.edu \
--cc=13653-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).