From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org, guile-devel@gnu.org
Subject: Re: [RFC] Block all async signals used by gdb when initializing Guile
Date: Sat, 29 Aug 2015 20:16:00 -0000 [thread overview]
Message-ID: <83wpwd26lt.fsf@gnu.org> (raw)
In-Reply-To: <CAP9bCMQmWmbLg9qZ3ZyVyTF=fBOB-sJtFAr1=OCC_g53aGYRUw@mail.gmail.com>
> 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.
next prev parent reply other threads:[~2015-08-29 20:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 17:23 Doug Evans
2015-08-29 19:11 ` Eli Zaretskii
2015-08-29 19:20 ` Doug Evans
2015-08-29 20:16 ` Eli Zaretskii [this message]
2015-08-29 20:40 ` Doug Evans
2015-08-29 21:04 ` Mark Kettenis
2015-08-30 2:42 ` Eli Zaretskii
2015-09-01 5:06 ` Doug Evans
2015-09-01 14:36 ` Eli Zaretskii
2015-09-01 15:22 ` Doug Evans
2015-09-01 15:50 ` Eli Zaretskii
2015-08-30 2:35 ` Eli Zaretskii
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=83wpwd26lt.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).