From unknown Sun Jun 22 11:43:10 2025 X-Loop: help-debbugs@gnu.org Subject: bug#24852: guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call" Resent-From: Christopher Allan Webber Original-Sender: "Debbugs-submit" Resent-CC: bug-guile@gnu.org Resent-Date: Tue, 01 Nov 2016 19:36:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: report 24852 X-GNU-PR-Package: guile X-GNU-PR-Keywords: To: 24852@debbugs.gnu.org X-Debbugs-Original-To: bug-guile@gnu.org Received: via spool by submit@debbugs.gnu.org id=B.14780289066628 (code B ref -1); Tue, 01 Nov 2016 19:36:02 +0000 Received: (at submit) by debbugs.gnu.org; 1 Nov 2016 19:35:06 +0000 Received: from localhost ([127.0.0.1]:39377 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1epu-0001io-Dy for submit@debbugs.gnu.org; Tue, 01 Nov 2016 15:35:06 -0400 Received: from eggs.gnu.org ([208.118.235.92]:37256) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1epr-0001iG-OZ for submit@debbugs.gnu.org; Tue, 01 Nov 2016 15:35:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c1epl-0007QE-PO for submit@debbugs.gnu.org; Tue, 01 Nov 2016 15:34:58 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=disabled version=3.3.2 Received: from lists.gnu.org ([2001:4830:134:3::11]:56920) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c1epl-0007QA-MJ for submit@debbugs.gnu.org; Tue, 01 Nov 2016 15:34:57 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56455) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1epk-0004Nj-Jv for bug-guile@gnu.org; Tue, 01 Nov 2016 15:34:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c1epg-0007PB-Mn for bug-guile@gnu.org; Tue, 01 Nov 2016 15:34:56 -0400 Received: from dustycloud.org ([50.116.34.160]:34242) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1epg-0007P4-Im for bug-guile@gnu.org; Tue, 01 Nov 2016 15:34:52 -0400 Received: from oolong (localhost [127.0.0.1]) by dustycloud.org (Postfix) with ESMTPS id E6E6B265F2 for ; Tue, 1 Nov 2016 15:34:51 -0400 (EDT) User-agent: mu4e 0.9.16; emacs 25.1.1 From: Christopher Allan Webber Date: Tue, 01 Nov 2016 14:34:51 -0500 Message-ID: <87k2cnat9g.fsf@dustycloud.org> MIME-Version: 1.0 Content-Type: text/plain X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 2001:4830:134:3::11 X-Spam-Score: -4.0 (----) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -4.0 (----) Build Guile master, then do: ./meta/guile --listen=/tmp/guile-socket Connect from emacs like so: M-x guile-connect-local You'll connect, but if you look at the shell you spawned Guile in, you'll see: ERROR: In procedure select: Interrupted system call You'll also find that where you would expect to have a working REPL, it's now blocked, and does not appear to become unblocked even after exiting the connected REPL. You also won't be able to spawn a second REPL via `guile-connect-local'. This doesn't happen in Guile's 2.0.X stable releases, only in latest master afaict. I wonder if it has something to do with recent changes in the way ports suspend? From unknown Sun Jun 22 11:43:10 2025 MIME-Version: 1.0 X-Mailer: MIME-tools 5.505 (Entity 5.505) X-Loop: help-debbugs@gnu.org From: help-debbugs@gnu.org (GNU bug Tracking System) To: Christopher Allan Webber Subject: bug#24852: closed (Re: bug#24852: guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call") Message-ID: References: <8760o6q4wl.fsf@dustycloud.org> <87k2cnat9g.fsf@dustycloud.org> X-Gnu-PR-Message: they-closed 24852 X-Gnu-PR-Package: guile Reply-To: 24852@debbugs.gnu.org Date: Tue, 01 Nov 2016 21:15:03 +0000 Content-Type: multipart/mixed; boundary="----------=_1478034903-22290-1" This is a multi-part message in MIME format... ------------=_1478034903-22290-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Your bug report #24852: guile --listen=3D/path/to/socket: "ERROR: In procedure select: Inte= rrupted system call" which was filed against the guile package, has been closed. The explanation is attached below, along with your original report. If you require more details, please reply to 24852@debbugs.gnu.org. --=20 24852: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D24852 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems ------------=_1478034903-22290-1 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at 24852-close) by debbugs.gnu.org; 1 Nov 2016 21:14:21 +0000 Received: from localhost ([127.0.0.1]:39492 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1gNx-0005kp-2H for submit@debbugs.gnu.org; Tue, 01 Nov 2016 17:14:21 -0400 Received: from dustycloud.org ([50.116.34.160]:35470) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1gNv-0005kj-9K for 24852-close@debbugs.gnu.org; Tue, 01 Nov 2016 17:14:19 -0400 Received: from oolong (localhost [127.0.0.1]) by dustycloud.org (Postfix) with ESMTPS id B6390265F2 for <24852-close@debbugs.gnu.org>; Tue, 1 Nov 2016 17:14:18 -0400 (EDT) References: <87k2cnat9g.fsf@dustycloud.org> User-agent: mu4e 0.9.16; emacs 25.1.1 From: Christopher Allan Webber To: 24852-close@debbugs.gnu.org Subject: Re: bug#24852: guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call" In-reply-to: <87k2cnat9g.fsf@dustycloud.org> Date: Tue, 01 Nov 2016 16:14:18 -0500 Message-ID: <8760o6q4wl.fsf@dustycloud.org> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -2.5 (--) X-Debbugs-Envelope-To: 24852-close X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.5 (--) Well, I was wrong. For some reason this stopped working for me over the last couple of days, but it doesn't seem to be Guile master that's at fault. I'm having the same trouble with Guile 2.0. Not sure how this started happening or why it's happening though... ------------=_1478034903-22290-1 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at submit) by debbugs.gnu.org; 1 Nov 2016 19:35:06 +0000 Received: from localhost ([127.0.0.1]:39377 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1epu-0001io-Dy for submit@debbugs.gnu.org; Tue, 01 Nov 2016 15:35:06 -0400 Received: from eggs.gnu.org ([208.118.235.92]:37256) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1epr-0001iG-OZ for submit@debbugs.gnu.org; Tue, 01 Nov 2016 15:35:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c1epl-0007QE-PO for submit@debbugs.gnu.org; Tue, 01 Nov 2016 15:34:58 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=disabled version=3.3.2 Received: from lists.gnu.org ([2001:4830:134:3::11]:56920) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c1epl-0007QA-MJ for submit@debbugs.gnu.org; Tue, 01 Nov 2016 15:34:57 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56455) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1epk-0004Nj-Jv for bug-guile@gnu.org; Tue, 01 Nov 2016 15:34:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c1epg-0007PB-Mn for bug-guile@gnu.org; Tue, 01 Nov 2016 15:34:56 -0400 Received: from dustycloud.org ([50.116.34.160]:34242) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1epg-0007P4-Im for bug-guile@gnu.org; Tue, 01 Nov 2016 15:34:52 -0400 Received: from oolong (localhost [127.0.0.1]) by dustycloud.org (Postfix) with ESMTPS id E6E6B265F2 for ; Tue, 1 Nov 2016 15:34:51 -0400 (EDT) User-agent: mu4e 0.9.16; emacs 25.1.1 From: Christopher Allan Webber To: bug-guile@gnu.org Subject: guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call" Date: Tue, 01 Nov 2016 14:34:51 -0500 Message-ID: <87k2cnat9g.fsf@dustycloud.org> MIME-Version: 1.0 Content-Type: text/plain X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 2001:4830:134:3::11 X-Spam-Score: -4.0 (----) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -4.0 (----) Build Guile master, then do: ./meta/guile --listen=/tmp/guile-socket Connect from emacs like so: M-x guile-connect-local You'll connect, but if you look at the shell you spawned Guile in, you'll see: ERROR: In procedure select: Interrupted system call You'll also find that where you would expect to have a working REPL, it's now blocked, and does not appear to become unblocked even after exiting the connected REPL. You also won't be able to spawn a second REPL via `guile-connect-local'. This doesn't happen in Guile's 2.0.X stable releases, only in latest master afaict. I wonder if it has something to do with recent changes in the way ports suspend? ------------=_1478034903-22290-1-- From unknown Sun Jun 22 11:43:10 2025 X-Loop: help-debbugs@gnu.org Subject: bug#24852: guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call" Resent-From: Christopher Allan Webber Original-Sender: "Debbugs-submit" Resent-CC: bug-guile@gnu.org Resent-Date: Wed, 02 Nov 2016 03:33:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 24852 X-GNU-PR-Package: guile X-GNU-PR-Keywords: To: 24852@debbugs.gnu.org Received: via spool by 24852-submit@debbugs.gnu.org id=B24852.14780575609911 (code B ref 24852); Wed, 02 Nov 2016 03:33:01 +0000 Received: (at 24852) by debbugs.gnu.org; 2 Nov 2016 03:32:40 +0000 Received: from localhost ([127.0.0.1]:39657 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1mI4-0002Zn-3p for submit@debbugs.gnu.org; Tue, 01 Nov 2016 23:32:40 -0400 Received: from dustycloud.org ([50.116.34.160]:36206) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1mI2-0002Ze-SQ for 24852@debbugs.gnu.org; Tue, 01 Nov 2016 23:32:39 -0400 Received: from oolong (localhost [127.0.0.1]) by dustycloud.org (Postfix) with ESMTPS id 782DB2671A for <24852@debbugs.gnu.org>; Tue, 1 Nov 2016 23:32:37 -0400 (EDT) References: <87k2cnat9g.fsf@dustycloud.org> <8760o6q4wl.fsf@dustycloud.org> User-agent: mu4e 0.9.16; emacs 25.1.1 From: Christopher Allan Webber In-reply-to: <8760o6q4wl.fsf@dustycloud.org> Date: Tue, 01 Nov 2016 22:32:36 -0500 Message-ID: <87lgx27e0b.fsf@dustycloud.org> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -2.5 (--) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.5 (--) Christopher Allan Webber writes: > Well, I was wrong. For some reason this stopped working for me over the > last couple of days, but it doesn't seem to be Guile master that's at > fault. I'm having the same trouble with Guile 2.0. > > Not sure how this started happening or why it's happening though... I figured out why I was experiencing this issue. It was a user issue... sort of. The behavior *is* reproducible but it wasn't a newly introduced bug (though it may be a bug). The difference between Guile stable and master experiencing the bug: I hadn't compiled Guile master with readline, so I disabled readline support in my ~/.guile file. Thus, the behavior "mysteriously" also started hapening in stable as well after this. Once I re-enabled it, the problem went away. So I guess hooking up readline somehow prevents this blocking prompt, though why, don't know!