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 22:32:36 -0500 [thread overview]
Message-ID: <87lgx27e0b.fsf@dustycloud.org> (raw)
In-Reply-To: <8760o6q4wl.fsf@dustycloud.org>
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!
prev parent reply other threads:[~2016-11-02 3:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 19:34 bug#24852: guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call" Christopher Allan Webber
2016-11-01 21:14 ` Christopher Allan Webber
2016-11-02 3:32 ` Christopher Allan Webber [this message]
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=87lgx27e0b.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).