From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 100224 invoked by alias); 29 Aug 2015 21:04:15 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 100215 invoked by uid 89); 29 Aug 2015 21:04:14 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: sibelius.xs4all.nl Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (83.163.83.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Sat, 29 Aug 2015 21:04:12 +0000 Received: from glazunov.sibelius.xs4all.nl (kettenis@localhost [127.0.0.1]) by sibelius.xs4all.nl (8.14.5/8.14.5) with ESMTP id t7TL42Ju029683; Sat, 29 Aug 2015 23:04:02 +0200 (CEST) Received: (from kettenis@localhost) by glazunov.sibelius.xs4all.nl (8.14.5/8.14.3/Submit) id t7TL42OS020892; Sat, 29 Aug 2015 23:04:02 +0200 (CEST) Date: Sat, 29 Aug 2015 21:04:00 -0000 Message-Id: <201508292104.t7TL42OS020892@glazunov.sibelius.xs4all.nl> From: Mark Kettenis To: xdje42@gmail.com CC: eliz@gnu.org, gdb-patches@sourceware.org, guile-devel@gnu.org In-reply-to: (message from Doug Evans on Sat, 29 Aug 2015 13:39:55 -0700) Subject: Re: [RFC] Block all async signals used by gdb when initializing Guile References: <831tel3o68.fsf@gnu.org> <83wpwd26lt.fsf@gnu.org> X-SW-Source: 2015-08/txt/msg00841.txt.bz2 > Date: Sat, 29 Aug 2015 13:39:55 -0700 > From: Doug Evans > > On Sat, Aug 29, 2015 at 1:16 PM, Eli Zaretskii wrote: > >> Date: Sat, 29 Aug 2015 12:20:24 -0700 > >> From: Doug Evans > >> Cc: "gdb-patches@sourceware.org" , guile-devel > >> > >> > 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. I suppose blocking these in the threads that guile starts is necessary because that is the only way to guarantee that those signals will be delivered to the main gdb thread on POSIX systems. On Windows you probably need to do something completely different.