From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Regression (last snapshot)
Date: Fri, 02 Aug 2019 15:04:00 -0000 [thread overview]
Message-ID: <20190802150412.GE11632@calimero.vinschen.de> (raw)
In-Reply-To: <b4d57d88-3ec4-939f-c591-e50aaef607f3@cornell.edu>
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
On Aug 2 14:34, Ken Brown wrote:
> On 8/1/2019 10:32 PM, Ken Brown wrote:
> > On 8/1/2019 5:17 PM, Ken Brown wrote:
> >> On 8/1/2019 12:04 PM, Corinna Vinschen wrote:
> >>> On Aug 1 10:38, Eric Blake wrote:
> >>>> Could it be a case of xwin-xdg-menu calling signal(SIGPIPE, SIG_IGN) or
> >>>> similar, and accidentally letting grep inherit the ignored SIGPIPE?
> >>>
> >>> execve doesn't propagate the signal dispositions, they get reset to
> >>> default.
> >>
> > I just built a version of grep in which I added 'signal(SIGPIPE, SIG_DFL)', and
> > the error is gone. So it looks like grep has in fact been receiving SIGPIPE,
> > and for some reason it is not using the default signal handler for SIGPIPE in a
> > terminal started by xwin-xdg-menu. Could this be a gtk issue? Does it mess
> > with the signal handlers?
>
> I think I've finally got it.
>
> First of all, here's what POSIX says about signal handlers after an exec:
>
> "Signals set to the default action (SIG_DFL) in the calling process
> image shall be set to the default action in the new process image.
> Except for SIGCHLD, signals set to be ignored (SIG_IGN) by the calling
> process image shall be set to be ignored by the new process image.
> Signals set to be caught by the calling process image shall be set to
> the default action in the new process image (see <signal.h>)."
Oh, I see. I misread the exceve man page. Only signals which are caught
will be reset to SIG_DFL. Sorry for the noise.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-02 15:04 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 22:55 Houder
2019-07-21 9:38 ` Houder
2019-07-21 9:42 ` Houder
2019-07-22 12:23 ` Ken Brown
2019-07-22 13:44 ` Ken Brown
2019-07-22 15:20 ` Corinna Vinschen
2019-07-22 15:53 ` Corinna Vinschen
2019-07-22 16:45 ` Corinna Vinschen
2019-07-22 18:47 ` Houder
2019-07-26 22:12 ` Ken Brown
2019-07-27 0:14 ` Ken Brown
2019-07-27 10:21 ` Houder
2019-07-27 15:24 ` Ken Brown
2019-07-27 16:25 ` Houder
2019-07-29 8:45 ` Corinna Vinschen
2019-07-29 13:18 ` Ken Brown
2019-07-29 13:35 ` Ken Brown
2019-07-29 13:48 ` Corinna Vinschen
2019-07-29 13:47 ` Corinna Vinschen
2019-07-29 14:26 ` Ken Brown
2019-07-29 15:23 ` Corinna Vinschen
2019-07-29 15:40 ` Corinna Vinschen
2019-07-29 18:56 ` Ken Brown
2019-07-31 15:53 ` Ken Brown
2019-07-31 18:00 ` Ken Brown
2019-08-01 9:01 ` Corinna Vinschen
2019-08-01 14:27 ` Jon Turney
2019-08-01 15:30 ` Ken Brown
2019-08-01 15:38 ` Eric Blake
2019-08-01 16:04 ` Corinna Vinschen
2019-08-01 21:17 ` Ken Brown
2019-08-02 2:32 ` Ken Brown
2019-08-02 14:34 ` Ken Brown
2019-08-02 15:04 ` Corinna Vinschen [this message]
2019-08-02 21:26 ` Brian Inglis
2019-08-02 21:53 ` Ken Brown
2019-08-02 21:58 ` Eric Blake
2019-08-03 3:50 ` Brian Inglis
2019-08-03 13:14 ` Ken Brown
2019-08-04 16:52 ` Houder
2019-08-01 10:03 ` Houder
2019-08-01 10:46 ` Houder
2019-08-01 12:20 ` Ken Brown
2019-08-01 14:29 ` Houder
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=20190802150412.GE11632@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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.
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).