From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4533 invoked by alias); 17 Feb 2014 21:13:55 -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 4523 invoked by uid 89); 17 Feb 2014 21:13:54 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout26.012.net.il Received: from mtaout26.012.net.il (HELO mtaout26.012.net.il) (80.179.55.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 17 Feb 2014 21:13:53 +0000 Received: from conversion-daemon.mtaout26.012.net.il by mtaout26.012.net.il (HyperSendmail v2007.08) id <0N1500700S5FH200@mtaout26.012.net.il> for gdb-patches@sourceware.org; Mon, 17 Feb 2014 23:12:15 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout26.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N15006W6S8EUX00@mtaout26.012.net.il>; Mon, 17 Feb 2014 23:12:15 +0200 (IST) Date: Mon, 17 Feb 2014 21:13:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH v2] Improved ^c support for gdb/guile In-reply-to: To: Doug Evans Cc: gdb-patches@sourceware.org, guile-devel@gnu.org Reply-to: Eli Zaretskii Message-id: <83y519788a.fsf@gnu.org> References: <834n3x8o7m.fsf@gnu.org> X-IsSubscribed: yes X-SW-Source: 2014-02/txt/msg00546.txt.bz2 > Date: Mon, 17 Feb 2014 12:59:22 -0800 > From: Doug Evans > Cc: "gdb-patches@sourceware.org" , guile-devel@gnu.org > > >> +void > >> +gdbscm_initialize_sigint (void) > >> +{ > >> + siscm_sigint_pipe[0] = siscm_sigint_pipe[1] = -1; > >> + > >> + if (!SCM_USE_PTHREAD_THREADS) > >> + { > >> + warning (_("Guile does not have pthreads support.")); > >> + warning (_("Proper SIGINT handling for Guile will be unavailable.")); > >> + return; > >> + } > > > > The above is what worries me. Guile currently doesn't work in the > > native MinGW build if configured with threads (it crashes, hangs, > > etc.). Can't we have decent SIGINT handling without pthreads? > > With 2.0.x, no. > I'm ok with changing the warning, e.g., not printing it at all on > systems where it would otherwise always be printed, and instead > documenting the issue for such systems. > > The downside is that while Scheme code is running SIGINT is ignored > (unless one is in the repl, or sets up a SIGINT handler oneself). Ignored why? because GDB sets the handler to SIG_IGN? Or for some other reason?