From: Alain Schneble <a.s@realize.ch>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: SIGTRAP in kill emulation on Windows
Date: Fri, 26 Aug 2016 11:47:36 +0200 [thread overview]
Message-ID: <86vaynhnev.fsf@realize.ch> (raw)
In-Reply-To: <83shtrdhb0.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 26 Aug 2016 12:13:07 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Alain Schneble <a.s@realize.ch>
>> CC: <emacs-devel@gnu.org>
>> Date: Fri, 26 Aug 2016 10:58:58 +0200
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> Yes, debugbreak and the proposed implementation behave identically.
>
> Then I guess that's a limitation we will have to live with. It
> doesn't sound like a grave one to me: after all, what exactly SIGTRAP
> does when no debugger is attached is not very important, since that is
> not the primary use case for that signal, AFAIU. If a Lisp program
> wants to kill the process, it doesn't need to use SIGTRAP.
I agree.
>> Yes, and on GNU/Linux I observed that it prints a backtrace prior to
>> termination.
>
> That depends on ulimit and suchlikes, I think: on a GNU/Linux system I
> tried that, the program was simply dumped to the shell prompt without
> printing anything.
Ok, thanks for the hint.
>> But that's kind of irrelevant here I guess. Where would be the best
>> place to document this quirk (c, signal-process, info manual)?
>
> Actually, perhaps not even there. In NEWS might be enough, I think.
Ok, I'll arrange a new patch with that added to the NEWS entry.
>> FWIW, there is probably something we could do about it -- query if the
>> process in question is attached to a debugger. If not, we could
>> terminate it.
>
> That's for the application to decide, IMO. Signal delivery is too
> low-level to replace one signal with another one.
That's a good point. I agree with you.
next prev parent reply other threads:[~2016-08-26 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 15:08 SIGTRAP in kill emulation on Windows Alain Schneble
2016-08-25 16:18 ` Eli Zaretskii
2016-08-25 20:02 ` Alain Schneble
2016-08-25 20:09 ` Alain Schneble
2016-08-26 8:24 ` Eli Zaretskii
2016-08-26 8:58 ` Alain Schneble
2016-08-26 9:13 ` Eli Zaretskii
2016-08-26 9:31 ` Eli Zaretskii
2016-08-26 9:47 ` Alain Schneble [this message]
2016-08-26 10:19 ` Alain Schneble
2016-10-08 13:54 ` Eli Zaretskii
2016-10-08 14:36 ` Alain Schneble
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=86vaynhnev.fsf@realize.ch \
--to=a.s@realize.ch \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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 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.