From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Regression (last snapshot)
Date: Sun, 04 Aug 2019 16:52:00 -0000 [thread overview]
Message-ID: <c3b303b4a25b450d11001479309b1574@smtp-cloud8.xs4all.net> (raw)
In-Reply-To: <b4d57d88-3ec4-939f-c591-e50aaef607f3@cornell.edu>
On Fri, 2 Aug 2019 14:34:02, Ken Brown wrote:
> 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>)."
>
> Second, here's a quote from the GTK+ documentation for gtk_init():
>
> "Since 2.18, GTK+ calls signal (SIGPIPE, SIG_IGN) during initialization,
> to ignore SIGPIPE signals, since these are almost never wanted in
> graphical applications. If you do need to handle SIGPIPE for some
> reason, reset the handler after gtk_init(), but notice that other
> libraries (e.g. libdbus or gvfs) might do similar things."
>
> Third, xwin-xdg-menu calls gtk_init() near the beginning of main().
>
> Putting this all together, Eric's explanation is indeed correct. All
> processes created by xwin-xdg-menu via fork/exec inherit the property of
> ignoring SIGPIPE.
>
> I don't know if this is a bug, but it certainly leads to surprising
> behavior. Jon, maybe xwin-xdg-menu needs to call signal(SIGPIPE,
> SIG_DFL) either after calling gtk_init() or before calling exec()?
Another option?
- https://bugs.python.org/issue1652 - see msg115364 (Author: Mitar)
# GHC Haskell compiler is currently opting for a different solution:
# installing an default empty handler which is cleared by exec
# automatically and signal handler is restored back to SIG_DFL:
#
# http://hackage.haskell.org/trac/ghc/ticket/4274
Installing the empty handler after the call to gtk_init() ...
Henri
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-08-04 16:52 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
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 [this message]
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=c3b303b4a25b450d11001479309b1574@smtp-cloud8.xs4all.net \
--to=houder@xs4all.nl \
--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).