bug#13018: fport_fill_input should handle EINTR

2013-08-08 Thread Mark H Weaver
This bug was fixed in fe51c7b3e0a1e93be3bb81dd2d4b18936fe2df3a. Thanks! Mark

bug#13018: fport_fill_input should handle EINTR

2013-07-03 Thread Mark H Weaver
We now finally understand the cause of this bug. See below. Andy Wingo writes: > On Thu 29 Nov 2012 21:19, l...@gnu.org (Ludovic Courtès) writes: > >> Aidan Gauland skribis: >> >>> fport_fill_input should handle an EINTR error from 'read', >>> and restart the read if that happens

bug#13018: fport_fill_input should handle EINTR

2013-03-29 Thread Aidan Gauland
> Aidan, do you have a test case? I haven't been able to reproduce this with a minimal example, but I can consistently reproduce it with my IRC bot . Replace the last two lines (lines 22 and 23) of run-cbot.scm with... (define bot (make-bot "Cunning_Bot"

bug#13018: fport_fill_input should handle EINTR

2013-03-13 Thread Andy Wingo
On Thu 29 Nov 2012 21:19, l...@gnu.org (Ludovic Courtès) writes: > Aidan Gauland skribis: > >> fport_fill_input should handle an EINTR error from 'read', >> and restart the read if that happens. >> >> by default on some systems, signals cause 'read', 'write', >> and

bug#13018: fport_fill_input should handle EINTR

2013-03-05 Thread Andy Wingo
On Wed 28 Nov 2012 09:19, Aidan Gauland writes: > In a program that maintains a TCP connection with a polling loop, I have > defined a signal handler with the `sigaction' procedure to terminate the > connection gracefully. When the trapped signal is received (in this > case SIGINT) and the handl

bug#13018: fport_fill_input should handle EINTR

2012-11-29 Thread Ludovic Courtès
Hi! Aidan Gauland skribis: > fport_fill_input should handle an EINTR error from 'read', > and restart the read if that happens. > > by default on some systems, signals cause 'read', 'write', > and many other system calls to abort and return an EINTR >

bug#13018: fport_fill_input should handle EINTR

2012-11-28 Thread Aidan Gauland
Guile version: 3.2.0-4-amd64 OS: Debian wheezy GNU/Linux, kernel 3.2.0-4-amd64 In a program that maintains a TCP connection with a polling loop, I have defined a signal handler with the `sigaction' procedure to terminate the connection gracefully. When the trapped signal is received (in this case