GNU bug report logs - #24852
guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call"

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 24852 in the body.
You can then email your comments to 24852 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Christopher Allan Webber <cwebber <at> dustycloud.org>
To: bug-guile <at> gnu.org
Subject: guile --listen=/path/to/socket: "ERROR: In procedure select:
 Interrupted system call"
Date: Tue, 01 Nov 2016 14:34:51 -0500

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?

Message #10 received at 24852-close <at> debbugs.gnu.org (full text, mbox):

From: Christopher Allan Webber <cwebber <at> dustycloud.org>
To: 24852-close <at> debbugs.gnu.org
Subject: Re: bug#24852: guile --listen=/path/to/socket: "ERROR: In procedure
 select: Interrupted system call"
Date: Tue, 01 Nov 2016 16:14:18 -0500

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...

Message #13 received at 24852 <at> debbugs.gnu.org (full text, mbox):

From: Christopher Allan Webber <cwebber <at> dustycloud.org>
To: 24852 <at> debbugs.gnu.org
Subject: Re: bug#24852: guile --listen=/path/to/socket: "ERROR: In procedure
 select: Interrupted system call"
Date: Tue, 01 Nov 2016 22:32:36 -0500

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!

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.