Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: $pipestatus broken?

X-seq: zsh-workers 29997
From: Frank Terbeck <ft@xxxxxxxxxxxxxxxxxxx>
To: zsh-workers@xxxxxxx
Subject: Re: $pipestatus broken?
Date: Sun, 11 Dec 2011 15:37:10 +0100
In-reply-to: <111210065833.ZM6198@torch.brasslantern.com> (Bart Schaefer's message of "Sat, 10 Dec 2011 06:58:33 -0800")
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
References: <87borgzkap.fsf@ft.bewatermyfriend.org> <877h24zj69.fsf@ft.bewatermyfriend.org> <111210065833.ZM6198@torch.brasslantern.com>

Bart Schaefer wrote:
[...]
> With that loop, I get a single "1" 100% of the time unless I attach to
> the process with GDB, in which case it becomes random.

I know I won't be much help in solving this, because I don't know how
any of the job handling code works or even what needs to be done for any
sort of sane job handling in the first place...

But I tried to see if I could pinpoint the revision, that introduced the
breakage. And it appears, that the first release that featured
`$pipestatus' was 3.1.7. And it's broken in that release already.

The first tag that includes the feature is `zsh-3.1.6-dev-21'. I tried
to build it, but I can't get the autotools (I tried various versions) to
produce a valid `configure' script. :-/

`$pipestatus' was introduced in workers-10358:

  <http://www.zsh.org/mla/workers/2000/msg01183.html>

Regards, Frank

References:
- $pipestatus broken?
  - From: Frank Terbeck
- Re: $pipestatus broken?
  - From: Frank Terbeck
- Re: $pipestatus broken?
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author