[debbugs-tracker] bug#24852: closed (guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call")

[GNU bug Tracking System]

Your message dated Tue, 01 Nov 2016 16:14:18 -0500
with message-id <address@hidden>
and subject line Re: bug#24852: guile --listen=/path/to/socket: "ERROR: In 
procedure select: Interrupted system call"
has caused the debbugs.gnu.org bug report #24852,
regarding guile --listen=/path/to/socket: "ERROR: In procedure select: 
Interrupted system call"
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24852: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24852
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> guile --listen=/path/to/socket: "ERROR: In procedure select: Interrupted system call"
>
>
>
>
> Date: 
>
> Tue, 01 Nov 2016 14:34:51 -0500
>
>
>
>
> User-agent: 
>
> mu4e 0.9.16; emacs 25.1.1
>
>
>
>
> 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?
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> 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
>
>
>
>
> User-agent: 
>
> mu4e 0.9.16; emacs 25.1.1
>
>
>
>
> 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...
>
>
> --- End Message ---