* bug#24852: guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call"
@ 2016-11-01 19:34 Christopher Allan Webber
2016-11-01 21:14 ` Christopher Allan Webber
0 siblings, 1 reply; 3+ messages in thread
From: Christopher Allan Webber @ 2016-11-01 19:34 UTC (permalink / raw)
To: 24852
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?
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#24852: guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call"
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
0 siblings, 1 reply; 3+ messages in thread
From: Christopher Allan Webber @ 2016-11-01 21:14 UTC (permalink / raw)
To: 24852-close
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...
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#24852: guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call"
2016-11-01 21:14 ` Christopher Allan Webber
@ 2016-11-02 3:32 ` Christopher Allan Webber
0 siblings, 0 replies; 3+ messages in thread
From: Christopher Allan Webber @ 2016-11-02 3:32 UTC (permalink / raw)
To: 24852
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!
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-11-02 3:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).