GNU bug report logs - #23000
send doesn't check for closed socket

Previous Next

Package: guile;

Reported by: Amirouche Boubekki <amirouche <at> hypermove.net>

Date: Sat, 12 Mar 2016 19:01:02 UTC

Severity: normal

Done: Andy Wingo <wingo <at> pobox.com>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 23000 in the body.
You can then email your comments to 23000 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guile <at> gnu.org:
bug#23000; Package guile. (Sat, 12 Mar 2016 19:01:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Amirouche Boubekki <amirouche <at> hypermove.net>:
New bug report received and forwarded. Copy sent to bug-guile <at> gnu.org. (Sat, 12 Mar 2016 19:01:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Amirouche Boubekki <amirouche <at> hypermove.net>
To: bug-guile <at> gnu.org
Subject: send doesn't check for closed socket
Date: Sat, 12 Mar 2016 19:57:35 +0100

[Message part 1 (text/plain, inline)]
The attached client.scm will crash with a SIGPIPE (based on strace) when 
run. It should raise an error instead.

The error happens when we try to send over socket that is closed on the 
other side.

Happens on 2.0 and master.

-- 
Amirouche ~ amz3 ~ http://www.hyperdev.fr
[client.scm (text/plain, attachment)]
[shared.scm (text/plain, attachment)]
[server.scm (text/plain, attachment)]
Information forwarded to bug-guile <at> gnu.org:
bug#23000; Package guile. (Tue, 03 May 2016 09:15:01 GMT) Full text and rfc822 format available.

Message #8 received at 23000 <at> debbugs.gnu.org (full text, mbox):

From: Amirouche Boubekki <amirouche <at> hypermove.net>
To: 23000 <at> debbugs.gnu.org
Subject: update from wingo
Date: Tue, 03 May 2016 11:07:58 +0200

wingo said:

> wingo | i don't think that's a guile bug -- i think in that case you 
> need to handle SIGPIPE
> wingo | b/c posix is weird
> wingo | (sigaction SIGPIPE SIG_IGN)
> wingo | the web server does it.
Reply sent to Andy Wingo <wingo <at> pobox.com>:
You have taken responsibility. (Mon, 20 Jun 2016 16:19:01 GMT) Full text and rfc822 format available.
Notification sent to Amirouche Boubekki <amirouche <at> hypermove.net>:
bug acknowledged by developer. (Mon, 20 Jun 2016 16:19:01 GMT) Full text and rfc822 format available.

Message #13 received at 23000-done <at> debbugs.gnu.org (full text, mbox):

From: Andy Wingo <wingo <at> pobox.com>
To: Amirouche Boubekki <amirouche <at> hypermove.net>
Cc: 23000-done <at> debbugs.gnu.org
Subject: Re: bug#23000: update from wingo
Date: Mon, 20 Jun 2016 18:18:05 +0200

tags 2300 +notabug
close
thanks

On Tue 03 May 2016 11:07, Amirouche Boubekki <amirouche <at> hypermove.net> writes:

> wingo said:
>
>> wingo | i don't think that's a guile bug -- i think in that case you
>> need to handle SIGPIPE
>> wingo | b/c posix is weird
>> wingo | (sigaction SIGPIPE SIG_IGN)
>> wingo | the web server does it.

Yep!
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Tue, 19 Jul 2016 11:24:03 GMT) Full text and rfc822 format available.
This bug report was last modified 8 years and 340 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.