From: Christopher Allan Webber <cwebber@dustycloud.org>
To: 24852@debbugs.gnu.org
Subject: bug#24852: guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call"
Date: Tue, 01 Nov 2016 14:34:51 -0500 [thread overview]
Message-ID: <87k2cnat9g.fsf@dustycloud.org> (raw)
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?
next reply other threads:[~2016-11-01 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 19:34 Christopher Allan Webber [this message]
2016-11-01 21:14 ` bug#24852: guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call" Christopher Allan Webber
2016-11-02 3:32 ` Christopher Allan Webber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2cnat9g.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=24852@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).