From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Doug Evans Newsgroups: gmane.lisp.guile.devel,gmane.comp.gdb.patches Subject: Re: [PATCH][PR guile/17247] Block SIGCHLD while initializing Guile Date: Mon, 1 Sep 2014 15:04:16 -0700 Message-ID: References: <834mwsh2nu.fsf@gnu.org> <8338ccgj78.fsf@gnu.org> <87ppffabw8.fsf@gnu.org> <83y4u3flr2.fsf@gnu.org> <87r3zv71qy.fsf@gnu.org> <83vbp7fer3.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1409609074 14467 80.91.229.3 (1 Sep 2014 22:04:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 1 Sep 2014 22:04:34 +0000 (UTC) Cc: =?UTF-8?Q?Ludovic_Court=C3=A8s?= , "gdb-patches@sourceware.org" , guile-devel To: Eli Zaretskii Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Tue Sep 02 00:04:27 2014 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 1XOZi3-0002sK-CO for guile-devel@m.gmane.org; Tue, 02 Sep 2014 00:04:23 +0200 Original-Received: from localhost ([::1]:34176 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOZi2-0005oR-P8 for guile-devel@m.gmane.org; Mon, 01 Sep 2014 18:04:22 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37797) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOZhz-0005nO-8y for guile-devel@gnu.org; Mon, 01 Sep 2014 18:04:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XOZhy-0006Mq-9H for guile-devel@gnu.org; Mon, 01 Sep 2014 18:04:19 -0400 Original-Received: from mail-yk0-x233.google.com ([2607:f8b0:4002:c07::233]:58341) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOZhy-0006M7-4a; Mon, 01 Sep 2014 18:04:18 -0400 Original-Received: by mail-yk0-f179.google.com with SMTP id 142so3562493ykq.38 for ; Mon, 01 Sep 2014 15:04:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=MHJMk2STbffsY1iPb/peBuIor+1m762xHjIA/UrHxxI=; b=QS6lqBz5ejn2fzvz1lHMpbcWee+DtrG8pVw+fqDpWvjhjM+5GjtLAbyHNb7nI8nrAt 6d5FL1b/GVZ27HoxyoR8kc1dY4Pt4sM28PXLmBrgcQmPnLy7SUsE3YK3XRdpehb9euLF 0INnuLH3FIGyf0EIlY66uBj5DYd4YAAfMFfQvJFQQ+66gn/b5WS+/W8ZCiptrYb/BFV9 EUgfLpfaHNM40kSsaI6VYwX2Rw8mG6ZnLr/gauoitgDMRizGbAKETkEUUVRgt3Zc/Enn f+ufgXyjlHuPIWtAw3LxI+vZPiPq1XrHaTx4UBcWzUZeTxmhdrmSsBPbvkRsvuA4vnLI bImQ== X-Received: by 10.236.142.7 with SMTP id h7mr5446954yhj.133.1409609057071; Mon, 01 Sep 2014 15:04:17 -0700 (PDT) Original-Received: by 10.170.66.138 with HTTP; Mon, 1 Sep 2014 15:04:16 -0700 (PDT) In-Reply-To: <83vbp7fer3.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4002:c07::233 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:17388 gmane.comp.gdb.patches:100425 Archived-At: On Mon, Sep 1, 2014 at 10:10 AM, Eli Zaretskii wrote: >> From: ludo@gnu.org (Ludovic Court=C3=A8s) >> Cc: gdb-patches@sourceware.org, guile-devel@gnu.org >> Date: Mon, 01 Sep 2014 18:18:45 +0200 >> >> Eli Zaretskii skribis: >> >> > Perhaps we should request GC and Guile to provide capabilities to >> > disable threads at run time, then. >> >> I don=E2=80=99t think we need to go this far: reading the recent discuss= ions, it >> seems Doug found a way to make sure Guile=E2=80=99s and libgc=E2=80=99s = internal threads >> don=E2=80=99t receive signals that GDB is interested in, which should be= enough >> for practical purposes. > > That's just the tip of an iceberg, I'm afraid. In the interests of seeking clarification early and clearly, can you elabor= ate? I'm not saying there aren't issues, I'm just wondering if you have anything specific that you are thinking of.