From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.lisp.guile.devel,gmane.comp.gdb.patches Subject: Re: [RFC] Block all async signals used by gdb when initializing Guile Date: Tue, 01 Sep 2015 17:35:08 +0300 Message-ID: <83lhcqcin7.fsf@gnu.org> References: <831tel3o68.fsf@gnu.org> <83wpwd26lt.fsf@gnu.org> <201508292104.t7TL42OS020892@glazunov.sibelius.xs4all.nl> <83si711oyo.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1441118177 2469 80.91.229.3 (1 Sep 2015 14:36:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Sep 2015 14:36:17 +0000 (UTC) Cc: guile-devel@gnu.org, gdb-patches@sourceware.org, mark.kettenis@xs4all.nl To: Doug Evans Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Tue Sep 01 16:36:09 2015 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZWmfQ-0004Gg-9S for guile-devel@m.gmane.org; Tue, 01 Sep 2015 16:36:08 +0200 Original-Received: from localhost ([::1]:54684 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWmfP-000082-FN for guile-devel@m.gmane.org; Tue, 01 Sep 2015 10:36:07 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50952) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWmfM-000072-63 for guile-devel@gnu.org; Tue, 01 Sep 2015 10:36:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZWmfI-0004lQ-Sq for guile-devel@gnu.org; Tue, 01 Sep 2015 10:36:04 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:47554) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWmfI-0004iw-Lj for guile-devel@gnu.org; Tue, 01 Sep 2015 10:36:00 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0NU0004005PG8U00@a-mtaout20.012.net.il> for guile-devel@gnu.org; Tue, 01 Sep 2015 17:34:57 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NU0003DT5U8UMC0@a-mtaout20.012.net.il>; Tue, 01 Sep 2015 17:34:57 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:17812 gmane.comp.gdb.patches:110749 Archived-At: > Date: Mon, 31 Aug 2015 22:05:59 -0700 > From: Doug Evans > Cc: Mark Kettenis , > "gdb-patches@sourceware.org" , guile-devel > > On Sat, Aug 29, 2015 at 7:37 PM, Eli Zaretskii wrote: > >> Date: Sat, 29 Aug 2015 23:04:02 +0200 (CEST) > >> From: Mark Kettenis > >> CC: eliz@gnu.org, gdb-patches@sourceware.org, guile-devel@gnu.org > >> > >> 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. > > > > I might be missing something, because I don't see why. > > The goal here is to block these signals from being sent to the threads > that Guile (or more specifically libgc) creates. Why only libgc? Don't we want to block these signals in any Guile code invoked later by GDB? > Not sure how to do that on windows. That problem doesn't exist on Windows, but what about Guile application threads launched later?