From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18159 invoked by alias); 17 Feb 2014 09:27:53 -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 18150 invoked by uid 89); 17 Feb 2014 09:27:52 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: glazunov.sibelius.xs4all.nl Received: from sibelius.xs4all.nl (HELO glazunov.sibelius.xs4all.nl) (83.163.83.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 17 Feb 2014 09:27:51 +0000 Received: from glazunov.sibelius.xs4all.nl (kettenis@localhost [127.0.0.1]) by glazunov.sibelius.xs4all.nl (8.14.5/8.14.3) with ESMTP id s1H9RgP5021335; Mon, 17 Feb 2014 10:27:42 +0100 (CET) Received: (from kettenis@localhost) by glazunov.sibelius.xs4all.nl (8.14.5/8.14.3/Submit) id s1H9RgXf020012; Mon, 17 Feb 2014 10:27:42 +0100 (CET) Date: Mon, 17 Feb 2014 09:27:00 -0000 Message-Id: <201402170927.s1H9RgXf020012@glazunov.sibelius.xs4all.nl> From: Mark Kettenis To: xdje42@gmail.com CC: gdb-patches@sourceware.org, guile-user@gnu.org, ludo@gnu.org In-reply-to: (message from Doug Evans on Mon, 17 Feb 2014 02:39:25 -0500) Subject: Re: [PATCH] Improved ^c support for gdb/guile References: X-SW-Source: 2014-02/txt/msg00530.txt.bz2 > From: Doug Evans > Date: Mon, 17 Feb 2014 02:39:25 -0500 > > Hi. > > Here's my modest contribution to the Guile anniversary potluck. > > The patch to selftest-support.exp could be done differently, > I've tried to keep it simple. The problem is that gdb with guile > will get SIGPWR from time to time when Guile's GC kicks in, > and we need this to not alter test behaviour. The patch just > tells the parent gdb to ignore SIGPWR, which is simple enough > without loss of coverage. A good question is what other signals > Guile GC might use. SIGPWR? Doesn't exist on *BSD. Guess it uses some other random signal there? Didn't realize Guile used threads. I guess that's safe if the interpreter makes sure it never calls into GDB code concurrently. But it does make debugging GDB harder. And I hope this is not an excuse for other people to start using threads in other bits of GDB.