unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: "no duplicate" in `popen.test'
Date: Tue, 18 Mar 2008 22:13:50 +0100	[thread overview]
Message-ID: <87bq5bka5t.fsf@gnu.org> (raw)
In-Reply-To: 87od9dc657.fsf@ossau.uklinux.net

Hi Neil,

Neil Jerram <neil@ossau.uklinux.net> writes:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hello,
>>
>> That "no duplicate" test in `popen.test' leaves a zombie behind it [0].
>> The fix would be to `waitpid' the process created by `open-input-pipe'
>> (see attached patch), but that makes it hang, waiting for "sleep 999" to
>> complete.
>
> I've attached an alternative possible solution, using feedback from
> the parent to the child to avoid needing the long sleep.

Good idea.

It apparently fixes the problem.  I think we also need that change in
the second "no duplicate" test, don't we?

> Unfortunately, though, I didn't manage to observe the zombie process
> with the test as it was before.  (How do I do this on GNU/Linux?)  So
> I don't really know whether this is a significant improvement.

You can just run "./check-guile && pstree -u $USER".  That shows whether
there are any processes left (whether zombie or not).  "ps" can then
tell whether these are zombies, when marked with a `Z'.

>> I'm not sure whether it's an indication that the bug was caught, or
>> rather an indication that the test is broken, especially since I don't
>> fully understand the bug that it's trying to catch.
>
> If waitpid fixes it, doesn't that point to the test being broken?

Hmm, I don't know, why?

Thanks,
Ludovic.





  reply	other threads:[~2008-03-18 21:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14 10:06 "no duplicate" in `popen.test' Ludovic Courtès
2008-03-17 22:55 ` Neil Jerram
2008-03-18 21:13   ` Ludovic Courtès [this message]
2008-05-19  8:53   ` Ludovic Courtès
2008-06-09 20:48     ` Neil Jerram
2009-05-19 23:56       ` Neil Jerram
2009-05-20 11:39         ` Ludovic Courtès
2009-05-20 17:44           ` 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=87bq5bka5t.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    /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).