Re: Test hang in Y01

[Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>]

On Sun, 11 Jan 2009 16:45:06 +1100
Geoff Wing <gcw@xxxxxxx> wrote:
> On Saturday 2009-01-10 21:48 +0000, Peter Stephenson output:
> :On Sat, 10 Jan 2009 10:44:49 -0500
> :"Vin Shelton" <acs@xxxxxxxxxxxxxxxxxxxx> wrote:
> :> With an up-to-date archive, I'm getting a hang in test Y01.
> :Haven't seen this with committed code, but I did get a hang in the
> :middle of changing it at one point.  Could you try "make clean" first?
> 
> Does it for me too.  My nightly build/test cron job first picked it up
> 12 hours ago so it only due to something in the last day or so.  It hangs
> with continuous CPU use.
> 
> #0  0xbbafba77 in read () from /usr/lib/libc.so.12
> #1  0xbbad0082 in bin_zpty (nam=0x80f96d0 "zpty", args=0xbfbe7784, ops=0xbfbe77f0, func=0) at zpty.c:573

There must be something screwy about the exit condition for the loop in
ptyread() such that read() is repeatedly being called but not returning
in such a way that the loop exits.  I did change this a few months ago,
noticed the condition was horrible, and tried to fix it up a bit without
being entirely sure what it was trying to do (you may have heard that
before...)

If "prog" is non-NULL at that point (which I can't see offhand), we are
more aggressive about continuing, but maybe need to trap some more
errors.  For example, if ret is -1 there may be (thinking about it,
almost certainly are) some values of errno where we need to exit the
loop.  Consequently it would probably be useful to find out what errno
was and if prog was non-NULL.

This is all guesswork.  I would put small amounts of money on this being
an existing race that's just shown up rather than a fundamentally new
bug that's just been introduced.

> BTW, the ChangeLog line for 26272 has some stuff elided.

Thanks, I've fixed this.

-- 
Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/