From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <xdje42@gmail.com>
Cc: guile-devel@gnu.org, gdb-patches@sourceware.org
Subject: Re: [RFC] Block all async signals used by gdb when initializing Guile
Date: Sun, 30 Aug 2015 05:35:44 +0300 [thread overview]
Message-ID: <83twrh1p1b.fsf@gnu.org> (raw)
In-Reply-To: <CAP9bCMRh+y4aNzgOThff5syzGs5-i2XpcbLVYw5G1avgd4QVvA@mail.gmail.com>
> Date: Sat, 29 Aug 2015 13:39:55 -0700
> From: Doug Evans <xdje42@gmail.com>
> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>, guile-devel <guile-devel@gnu.org>
>
> On Sat, Aug 29, 2015 at 1:16 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> Date: Sat, 29 Aug 2015 12:20:24 -0700
> >> From: Doug Evans <xdje42@gmail.com>
> >> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>, guile-devel <guile-devel@gnu.org>
> >>
> >> > What about platforms that don't have sigprocmask, but do have SIGINT?
> >> > Don't we want to block SIGINT on those platforms?
> >>
> >> Do they have threads
> >
> > They might. (The only way I've succeeded to have a working Guile on
> > Windows was to disable threads, but I hope that bug will be fixed one
> > day.)
> >
> >> and how does one block SIGINT on those platforms?
> >
> > With a call to 'signal', I guess.
>
> I'm guessing that won't work here, we'll need something else.
I don't understand why. Can you explain? Maybe I'm missing
something.
> The issue is we need the threads that guile starts
> to have these signals blocked. Then after guile init
> returns we unblock the signals.
Inhibit SIGINT ech time before calling Guile and restore it after
Guile returns. Wouldn't that do what you want?
prev parent reply other threads:[~2015-08-30 2:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 17:22 [RFC] Block all async signals used by gdb when initializing Guile Doug Evans
2015-08-29 19:11 ` Eli Zaretskii
2015-08-29 19:20 ` Doug Evans
2015-08-29 20:16 ` Eli Zaretskii
2015-08-29 20:39 ` Doug Evans
2015-08-29 21:04 ` Mark Kettenis
2015-08-30 2:37 ` Eli Zaretskii
2015-09-01 5:05 ` Doug Evans
2015-09-01 14:35 ` Eli Zaretskii
2015-09-01 15:22 ` Doug Evans
2015-09-01 15:50 ` Eli Zaretskii
2015-08-30 2:35 ` Eli Zaretskii [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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83twrh1p1b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guile-devel@gnu.org \
--cc=xdje42@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.
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).