From: John Proctor <john.proctor@gmail.com>
To: Detlev Zundel <dzu@denx.de>, Andy Wingo <wingo@pobox.com>
Cc: bug-guile mailing list <bug-guile@gnu.org>
Subject: Re: Problem with netcat
Date: Mon, 11 Apr 2011 13:35:18 -0400 [thread overview]
Message-ID: <BANLkTi=Zws9AK-FnE8QOfsPYM+BbePE3xQ@mail.gmail.com> (raw)
In-Reply-To: <m2r598dfjg.fsf@ohwell.denx.de>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
Thanks for the great response.
On Mon, Apr 11, 2011 at 10:32 AM, Detlev Zundel <dzu@denx.de> wrote:
> Hi Andy,
>
> > On Thu 07 Apr 2011 18:04, Detlev Zundel <dzu@denx.de> writes:
> >
> >> So it seems like guile wants simply to output a newline but the socket
> >> is closed already and the process then gets the SIGPIPE signal which
> >> guile is not prepared for.
> >
> > Excellent debugging, Detlev! I pushed a (sigaction SIGPIPE SIG_IGN) to
> > (system repl repl), which should fix the issue. Thanks for the
> > debugging, and thanks for the report, John!
>
> Thanks for the fix - I can confirm that this works (guile survives) for
> the cases where I saw the sigpipe before.
>
> Cheers
> Detlev
>
> --
> I had nothing to do with implementing Gosmacs. It was inspired
> by the original Emacs, but that's all. I would never have agreed
> to use a language like Mocklisp.
> -- Richard Stallman in <E1CUySS-00048D-RN@fencepost.gnu.org>
>
[-- Attachment #2: Type: text/html, Size: 1485 bytes --]
next prev parent reply other threads:[~2011-04-11 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 21:23 Problem with netcat John Proctor
2011-04-04 21:16 ` Andy Wingo
2011-04-06 10:52 ` Detlev Zundel
[not found] ` <BANLkTimDrGF+3TQdXzwjQ-mWbUj1VMYA6g@mail.gmail.com>
2011-04-07 16:04 ` Detlev Zundel
2011-04-11 8:14 ` Andy Wingo
2011-04-11 14:32 ` Detlev Zundel
2011-04-11 17:35 ` John Proctor [this message]
2011-04-11 17:36 ` Mark H Weaver
2011-04-11 18:03 ` Andy Wingo
2011-04-13 9:08 ` Detlev Zundel
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='BANLkTi=Zws9AK-FnE8QOfsPYM+BbePE3xQ@mail.gmail.com' \
--to=john.proctor@gmail.com \
--cc=bug-guile@gnu.org \
--cc=dzu@denx.de \
--cc=wingo@pobox.com \
/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).