unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Fix hanging of popen.test
Date: Mon, 14 Jun 2010 23:27:13 +0200	[thread overview]
Message-ID: <m3aaqxl2z2.fsf@pobox.com> (raw)
In-Reply-To: <87vd9p5p07.fsf@ossau.uklinux.net> (Neil Jerram's message of "Fri, 11 Jun 2010 20:48:56 +0100")

Heya Neil,

On Fri 11 Jun 2010 21:48, Neil Jerram <neil@ossau.uklinux.net> writes:

> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> +(close-port (current-input-port))
>> +(let loop ()
>> +  (display "closed\n" (current-error-port))
>> +  (force-output  (current-error-port)))
>
> Oops, missing a `(loop)' at the end there.  I'll see if the test still
> works after adding that in.

It was an interesting analysis, though I admit I didn't follow all of
it. The SIGPIPE didn't hit the subprocess because bash was doing
something strange? How did your new test work out?

Regards,

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2010-06-14 21:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 22:54 [PATCH] Fix hanging of popen.test Neil Jerram
2010-06-11 19:48 ` Neil Jerram
2010-06-14 21:27   ` Andy Wingo [this message]
2010-06-28 21:48     ` Neil Jerram
2010-06-29  9:31       ` Andy Wingo
2010-06-29 19:11         ` Neil Jerram
2010-06-30 22:50           ` Neil Jerram
2010-06-30 23:58             ` Neil Jerram
2010-07-01 10:48               ` Andy Wingo
2010-07-01 20:29                 ` Patrick McCarty
2010-07-03 22:17                 ` Ludovic Courtès
2010-07-04  9:07                   ` Andy Wingo
2010-07-04 20:33                 ` Neil Jerram
2010-07-06 21:35                   ` Ludovic Courtès
2010-07-17 11:57                   ` Andy Wingo
2010-07-17 18:08                     ` Patrick McCarty
2010-07-01 16:22             ` dsmich
2010-07-01 21:22               ` Neil Jerram

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=m3aaqxl2z2.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=neil@ossau.uklinux.net \
    /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).