From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Mark H Weaver Newsgroups: gmane.lisp.guile.bugs Subject: bug#32367: 2.2.4 hangs when a script uses a module that calls sigaction Date: Wed, 22 Aug 2018 22:20:21 -0400 Message-ID: <87va81bz8a.fsf@netris.org> References: <87pnyx4p2q.fsf@priss.frightenedpiglet.com> <877el36crs.fsf@teapot.weinholt.se> <8760032yri.fsf@netris.org> <87pnya5x8a.fsf@priss.frightenedpiglet.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1534991665 7251 195.159.176.226 (23 Aug 2018 02:34:25 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 23 Aug 2018 02:34:25 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) Cc: 32367@debbugs.gnu.org, Ludovic =?UTF-8?Q?Court=C3=A8s?= , =?UTF-8?Q?G=C3=B6ran?= Weinholt To: Derek Upham Original-X-From: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Thu Aug 23 04:34:21 2018 Return-path: Envelope-to: guile-bugs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fsfS0-0001kW-OQ for guile-bugs@m.gmane.org; Thu, 23 Aug 2018 04:34:20 +0200 Original-Received: from localhost ([::1]:34081 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fsfU5-0007pr-K3 for guile-bugs@m.gmane.org; Wed, 22 Aug 2018 22:36:29 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36364) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fsfTv-0007op-Vx for bug-guile@gnu.org; Wed, 22 Aug 2018 22:36:23 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fsfH4-0006UV-0W for bug-guile@gnu.org; Wed, 22 Aug 2018 22:23:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:53191) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fsfH3-0006UN-TP for bug-guile@gnu.org; Wed, 22 Aug 2018 22:23:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fsfH3-0000oL-NX for bug-guile@gnu.org; Wed, 22 Aug 2018 22:23:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Mark H Weaver Original-Sender: "Debbugs-submit" Resent-CC: bug-guile@gnu.org Resent-Date: Thu, 23 Aug 2018 02:23:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32367 X-GNU-PR-Package: guile X-GNU-PR-Keywords: Original-Received: via spool by 32367-submit@debbugs.gnu.org id=B32367.15349909233007 (code B ref 32367); Thu, 23 Aug 2018 02:23:01 +0000 Original-Received: (at 32367) by debbugs.gnu.org; 23 Aug 2018 02:22:03 +0000 Original-Received: from localhost ([127.0.0.1]:58208 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fsfG6-0000mR-Td for submit@debbugs.gnu.org; Wed, 22 Aug 2018 22:22:03 -0400 Original-Received: from world.peace.net ([64.112.178.59]:39480) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fsfG5-0000ly-J1 for 32367@debbugs.gnu.org; Wed, 22 Aug 2018 22:22:01 -0400 Original-Received: from mhw by world.peace.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1fsfFz-0002GR-ST; Wed, 22 Aug 2018 22:21:55 -0400 In-Reply-To: <87pnya5x8a.fsf@priss.frightenedpiglet.com> (Derek Upham's message of "Wed, 22 Aug 2018 06:47:49 -0700") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-guile@gnu.org List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Original-Sender: "bug-guile" Xref: news.gmane.org gmane.lisp.guile.bugs:9124 Archived-At: Hi Derek, Derek Upham writes: > Thanks. I built from 4c91de3e4 and was able to reproduce the problem. > Then I reverted 761cf0fb8c364e885e4c6fced34563f8157c3b84 and I was not > able to reproduce it. Thanks for checking. I've reopened which led to the faulty commit, and sent some messages there proposing a rough outline for a more proper fix. Mark