From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-125725-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 80880 invoked by alias); 29 Aug 2015 20:40:01 -0000
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
Received: (qmail 80838 invoked by uid 89); 29 Aug 2015 20:40:01 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-yk0-f173.google.com
Received: from mail-yk0-f173.google.com (HELO mail-yk0-f173.google.com) (209.85.160.173) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Sat, 29 Aug 2015 20:39:57 +0000
Received: by ykbu129 with SMTP id u129so13838130ykb.2        for <gdb-patches@sourceware.org>; Sat, 29 Aug 2015 13:39:55 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.129.71.69 with SMTP id u66mr14819931ywa.49.1440880795250; Sat, 29 Aug 2015 13:39:55 -0700 (PDT)
Received: by 10.13.254.195 with HTTP; Sat, 29 Aug 2015 13:39:55 -0700 (PDT)
In-Reply-To: <83wpwd26lt.fsf@gnu.org>
References: <m3r3mmdn7g.fsf@sspiff.org>	<831tel3o68.fsf@gnu.org>	<CAP9bCMQmWmbLg9qZ3ZyVyTF=fBOB-sJtFAr1=OCC_g53aGYRUw@mail.gmail.com>	<83wpwd26lt.fsf@gnu.org>
Date: Sat, 29 Aug 2015 20:40:00 -0000
Message-ID: <CAP9bCMRh+y4aNzgOThff5syzGs5-i2XpcbLVYw5G1avgd4QVvA@mail.gmail.com>
Subject: Re: [RFC] Block all async signals used by gdb when initializing Guile
From: Doug Evans <xdje42@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>, guile-devel <guile-devel@gnu.org>
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
X-SW-Source: 2015-08/txt/msg00840.txt.bz2

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.
The issue is we need the threads that guile starts
to have these signals blocked. Then after guile init
returns we unblock the signals.